yashsingh1/xdaforums huggingface dataset:
[Huawei P20 Lite Questions & Answers] ars_chelsea:
Hi there :)

Do you know your build number? eg: C432 is for europe in general.

Do you know your exact model? eg: ANE-LX1

So basically you can't access recovery(via power+Volume up) and fastboot(via power+Volume down) ?? That's weird, but if you don't wanna wait, you can just do this procedure by [MENTION=6688482]Merlin_99[/MENTION] : https://xdaforums.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557

And do everything except "Finally, enter to the project menu from dialer typing *#*#2846579#*#* ==> Software Upgrade ==> SdCard Upgrade.

Wait for the installation and before configuring the device enter in Recovery Mode (from the phone off, VOLUME-UP + POWER ON) and make Wipe Cache Partition, Wipe Data/Factory Reset, Reboot System Now." which is not needed since you can't boot.

Now after you copied the file to your sd card, just press power+volume down+volume up at the same time until the Huawei logo disappears and it starts applying the update.

Cheers and hope for the best,

AS
[Huawei P20 Lite Questions & Answers] salimkop:
Thank you, nice from you. Now i can acced to the recovery mode, when i do a factory resert, it's stuck at 0%, how can i solve that ?
[Nokia 8 Questions & Answers] RaleBurazer:
Hello, does anybody happen to have a link to a Stable Pie update, and can they also post a guide on installing it. Thanks in advance!
[Nokia 8 Questions & Answers] Sahilsinghlodhi:
https://android.googleapis.com/pack.../59bd9a533025ca61629b32eb85fd6e410705c1dc.zip

Download the zip

Boot to stock recovery,

And use command ADB sideload update.zip from console.
[Nokia 8 Questions & Answers] RaleBurazer:
Thank you sir/ma'am! Will this work on TA-1012?
[Nokia 8 Questions & Answers] Sahilsinghlodhi:
Yes it'll work.
[Nokia 8 Questions & Answers] RaleBurazer:
Okay and just because I'm paranoic, this is official update, not leaked/beta? Sorry if I'm annoying

Edit: Thanks Sir/Ma'am! It works!
[Nokia 8 Questions & Answers] galvakojis:
well "Stable Pie" does not exist :D
[Nokia 8 Questions & Answers] RaleBurazer:
Unbelievable.
[Nokia 8 Questions & Answers] galvakojis:
looks like it is true
[Xiaomi Mi A1 Questions & Answers] lucask28d:
Hey, al already had this problem.

Try to boot the TWRP using BootLoader with command bootloader boot_a file.img (i belive that the command is this one, if does't you can find on TWRP tread), and boot again the rom that had failed.

If doesn't work, you probably will need to boot files like modem.img, firmware or others that may be corrupted cause of flashing.

There are actually a lot of treads of similar erros that happens on honor phones or oneplus, you can use them as reference tho find witch are the files that cause the non recognition on USB after a failed flash.

If needed reflash stock, it will fix in last case.
[Android Q&A, Help & Troubleshooting] ozkinay:
Hello.

I have a car head unit which runs Android 5. But it is so slow that can not work latest Google Maps. It really gets strokes after updating Google Play Services. And also has some instable actions. It crashes or stops, i think because of insufficient sources. I want to use Spotify and Google Maps but it takes almost 20 seconds for just Google Maps to open.

I think updating my Android from 5 to 6 may solve my problems. Or maybe updating to a simpler, lighter but faster one. (Dont know which or what...)

How can I update my Android version? How can I fasten this device?

I am attaching the photos of technicals of my device.

Please help. Thanks.
[Android Q&A, Help & Troubleshooting] ozkinay:
Nobody to help? :(
[Android Q&A, Help & Troubleshooting] ozkinay:
65 views and no answer...
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] t---pl:
Hello!

the issue:

My device s4 mini (serranoltexx) does not boot further than the initial Samsung logo (showing the "normal" warranty kernel in the left top end of the screen), and then turns black. I can't do anything beyond this stage. When I take out the battery and insert it again, the device boots /starts automatically until the samsung sign and turns black again.

the background:

Last year in July, I flashed mys4 mini (serranoltexx) using odin, twrp and one of the latest official lineageOS Roms 14.1 (July 2018), with nano gapps. But since this morning (10. of January 2019), I can't start my device anymore. The latest update, which I did for the ROM was in July. Due to work reasons and since the official maintenance expired, I did not follow any other Lineage updates for my device, e.g. on this website. But I could use my device daily without any problems until this morning, when I started an app (music player) and after a few tones, the music stopped and the device turned black. Since then I could not enter or boot my device properly. I use a 32gb sd card as an integrated storage.

steps already done:

I tried to enter the recovery mode. When switching it on (taking the battery out and back in), I can enter the initial screen of the recovery mode, but after may be 3 to 5 seconds it turns black again. Saying nothing. I intended to flashed fresh using odin and twrp, and then the latest lineageOS ROM versions from your website. But the same sequence happened again: After using the key sequence for entering the download mode, I can enter it and push the volume up button, but then the device turns black again, saying and reacting to nothing. I changed the batteries (I have several), but it did not change anything. And this puzzles me ....

I know that my device updated trwp yesterday - when my device was still working - but I turned it off and I could turn it one this morning functioning well until I used an app.

the question /the request:

Is there any possibility to fix this problem? Could anyone help me on this issue, please. I really like my s4 mini, I do not want throw it away. I would really appreciate any advice which would possibly fix my problems.

Many thanks in advance for your replies and help
[Samsung Galaxy S7 Questions and Answers] GreeTech:
I would really like to root my phone to get access to the Android 9.0 features, but I don't want to lose the stock camera. I know GCam port exists, but there are things that it can't do that I like doing on the stock cam. So is there any hope we can use it on an S9 version? Or would Samsung need to do that?
[Samsung Galaxy S7 Questions and Answers] Beanvee7:
Only way to use the Samsung Camera would be to be on Samsung's Android, due to proprietary code that powers the camera.

If you want Android 9.0 features, and the Samsung camera, you'd need a 9.0 ROM port from the Note or S9, which don't exist because 9.0 hasn't arrived on these devices yet.

If you only want the latest camera, there's usually camera ports like https://xdaforums.com/galaxy-s8/themes/port-samsung-s9-camera-port-ar-emoji-t3826284
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.

I've tried many unofficial ROMs, but still getting the same message!!!

And when I tried to use the official ROM, the upgrade stopped on 11%!!??

To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
What "official" ROM? You've given absolutely NO info regarding anything friend...

Myself, I'd click the green link in my signature... but that's me :cool:
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!

Kindly, advice if you have any solution or ask for a specific info.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
Fine,,,

Device: at&t 8525

ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).

The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.

So, the device still having no GSM.

Thank You....
[8525, TyTN, MDA Vario II, JasJam ROM Development] wacky.banana:
FirasKB,

Most roms on her DO NOT come with a radio included. Usually only the manufacturer roms do.

There are 2 things you need to do:

- Consult the MrVanx guides which will help you understand what you are doing (google search for this).

- go to the wiki in this forum and search for a radio rom to upload.

In summary, reflash, say, Scahps rom then flash a radio rom from the wiki (I suggest radio 1.47, which is pretty reliable).

Hope this helps.

WB
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
Ahhh, a little info. :rolleyes:

First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.

Reboot the pc with the PDA disconnected.

(Oh, make sure that you have ActiveSync 4.5 insttalled of course)

Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)

Connect the PDA to the USB cable and run the RUU_Inside.exe file.

wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.

I can't guarantee that this will work but it IS your best shot friend.

Good luck!
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
Thanks to your support friends,,

I've done as you mentioned, but the upgrade process stopped on 11% again and couldn't complete!!?? (the message ERROR [262]: UPDATE ERROR appeared on my P.C)!!??

Kindly, advice...
[8525, TyTN, MDA Vario II, JasJam ROM Development] wacky.banana:
I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)

Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.

WB
[8525, TyTN, MDA Vario II, JasJam ROM Development] jphilcarp:
Stuck.... completely stuck

My fiances phone is stuck in the tri color bootloader screen. I am in the US and i have tried everything from flashing the original RUU to a hard reset and everthing, but nothing seems to work. the IPL is 4. 10. 0002 and the SPL is 4. 10. 0000. Can someone please help me. I know there has to be a way to fix this.
[8525, TyTN, MDA Vario II, JasJam ROM Development] nemets:
I had the same problem. After trying to fix it myself for about a week I gave up and sent it to AT&T Repair center. Got it back functional.

I haven't tried the Himalaya ROM method, though.

Check this thread:

http://xdaforums.com/showthread.php?t=372895

Good luck!
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
Thanks again to your support,

The problem happened when I tried to unlock the device to upgrade it (it was fine befor), I don't know whether it was already locked or not, but usualy when I buy any Pocket P.C I'm preparing to unlock it first (I've done that many times on HERMES before, but this is the first time I'm facing such problem!!). So, while unlocking the device it's stucked on the tri color screen.

I've done many things after that to solve the problem (updating the hard SPL to v2.10 successfully, flashing many ROMs -not including Radio- successfully).

So, I can flash any ROM now but it must be without Radio, otherwise the flashing process will stuck on 11%.
[8525, TyTN, MDA Vario II, JasJam ROM Development] JR_de:
try reading the wiki:

http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.
[8525, TyTN, MDA Vario II, JasJam ROM Development] wacky.banana:
FirasKB,

What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.

WB
[8525, TyTN, MDA Vario II, JasJam ROM Development] Abo Forat:
Schap´s Rom has NO Radio. Flash this one

BUT u must have HardSPL

http://xdaforums.com/showthread.php?t=348435&highlight=Radio
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
wacky.banana,

As I wrote above, my problem still not solved :confused: and my device still running with (No GSM).

I've done the following:

- Updating the ROM (O.S only as the device not accepting any Radio ROM)

- Updating the SPL to Version 7.

- Trying to update the radio (separately) but I didn't success??!!

It seems there is no solution to fix this problem???!!!
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
No way, I tried it but my device can't accept any Radio version.
[8525, TyTN, MDA Vario II, JasJam ROM Development] wacky.banana:
Frisk,

Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://xdaforums.com/archive/index.php/t-298516.html

Cheers

WB
[8525, TyTN, MDA Vario II, JasJam ROM Development] FirasKB:
Unfortunately, but that's also didn't help, because the main problem now is how to install the Radio on the device??!!

The device is not accepting the Radio installation at all, NO WAY....
[Samsung Galaxy Tab A series Questions & Answers] Sykoknot:
I have the Galaxy Tab A 10.1 SM-t580. It was on 8.0 stock prior to this. I attempted to flash TWRP a couple of ways to no avail. I did a factory reset and attempted another method, but I believe I forgot to turn on OEM Unlock after the reset. Odin now will flash a TWRP successfully, but trying to boot into recovery either loops or presents me with glitchy horizontal lines. Trying to flash the 7.0 stock firmware (XAR) from Sammobile results in failure (maybe because it has an older bootloader?). I've tried just the AP, AP and BL, and AP, BL, and CSC. They all fail. There doesnt appear to be any working OS on the device at this point. The only thing I can access is download mode.

After trying the flash stock firmware I get this message in odin:

<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

and in download mode I have the following messages at the top:

ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-T580
CURRENT BINARY: Custom
SYSTEM STATUS: Official
FRP LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x0500)
RP SWERV: B:4 K:1 S:2
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 2

Any help would be super appreciated.
[Samsung Galaxy Tab A series Questions & Answers] Sykoknot:
Took a lot of figuring out. But My bootloader would only accept the latest version of the stock firmware (Oreo) and I had to dig to find a working TWRP. If anyone has any questions I gothca.
[Samsung Galaxy Tab A series Questions & Answers] jordansays:
I was having the same issue and bricked/unbricked my tablet a few times before figuring out it will only take the latest firmware. Which version of TWRP worked?

I'm trying to downgrade as the last update caused an "Authentication Error" every time I tried to connect to wifi.
[Samsung Galaxy Tab A series Questions & Answers] buriburi69:
Did you find a working TWRP for Oreo? Can you post the link or say the versión of TWRP?

I used the twrp-3.2.3-0-gtaxlwifi.img.tar (lastest by now) but only had the red vertical lines in recovery mode

---------- Post added at 01:11 PM ---------- Previous post was at 12:47 PM ----------

Same problem and I solved it flashing the content of this file CF-Auto-Root-gtaxlwifi-gtaxlwifixx-smt580.zip

Extrated from this documentation: w ww.techmoviles.com/rootear-galaxy-tab-a-sm-t580-sm-t585-con-cf-auto-root/ (fix the blank between the w)

This flash don't load a working TWRP in oreo, (because it is for nougat), but it fixes the recovery on oreo restoring the Android recovery.

I hope it helps you
[Samsung Galaxy Tab A series Questions & Answers] xballumx:
OK. Got given a TAB 10.1 a few weeks back and decided to boot up Odin for the first time since my Note3. Hated the Samsung stock ROM so went through the same journey of trying to install TWRP over Android 8 only to find it soft bricks the tab. EVENTUALLY realised I could only recover with Android 8 which i have.

SO question is can I install TWRP over Android 8 or do i have to downgrade. If yes to a downgrade is it just a case of grabbing Android 7 off Sammobile?

Thanks in advance.
[Samsung Galaxy Tab A series Questions & Answers] RedNas74:
Use this TWRP. It should work: https://xdaforums.com/showpost.php?p=78148216&postcount=169
[Samsung Galaxy Tab A series Questions & Answers] Nimueh:
There was a newer one on the same day though - it's what I'm using and it works fine :)

Then again my tablet was on stock Nougat - so no idea if [MENTION=3748422]xballumx[/MENTION] can use it on Oreo ... but I don't see why not since it still works on an Oreo custom rom :fingers-crossed:
[Samsung Galaxy Tab A series Questions & Answers] wahidkurdo:
Hey bro

you are using the wrong flash file your phone Binary is 4

check that the flash file name contains U4
[Samsung Galaxy Tab A series Questions & Answers] Nimueh:
Pretty sure that over a year and a half later they've sorted their issues ... or threw the device under a moving truck already :laugh:
[General Questions and Answers] StardustDroid:
Hi folks,

I tried to install MicroG-LineageOS14.1 https://download.lineage.microg.org/a5y17lte/ but noticed that SIM card, IMEI are not recognized with this ROM.

So I decided to going back to stock Android8 Oreo, but now, SIM card is recognized, but I don't have any IMEI number if I call *#06# or by looking in phone information.

What can I do to recover the IMEI ? I have a Nandroid backup of LineageOS 14.1, maybe /efs (if it's the good partition) have the good informations ?

(I know my real IMEI number)

Any hint to recover my phone please ?

Regards
[General Questions and Answers] StardustDroid:
OK, figured myself by searching, reading, digging a lot:

restored /efs partition (2MB) from my Nandroid backup of Lineage14.1 had worked

W00t !
[General Questions and Answers] codenewbie:
hello, i have the same problem and no backup. Any ideas on how i can solve this?
[Google Pixel 2 XL Questions & Answers] urinsane:
I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.

I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.

Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.

I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:

"FAILED (remote: 'Flashing Unlock is not allowed')"

I've tried Deuce's script, same errors.

Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.

Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.

I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.

My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!
[Google Pixel 2 XL Questions & Answers] Didit_Anshari:
So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?
[Google Pixel 2 XL Questions & Answers] urinsane:
Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).
[Google Pixel 2 XL Questions & Answers] ASMstudent:
I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
Yes. Google is rather lenient in that regard.
[Google Pixel 2 XL Questions & Answers] ASMstudent:
That's good news!

Do they require a proof of purchase or a warranty card because I don't have either of them.
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.
[Google Pixel 2 XL Questions & Answers] ASMstudent:
I found out that this happen when I press volume up while the device Boots up.

First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
[Google Pixel 2 XL Questions & Answers] Badger50:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else? :confused:
[Google Pixel 2 XL Questions & Answers] ASMstudent:
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.
[Google Pixel 2 XL Questions & Answers] ASMstudent:
Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.