I have a Lenovo TB-X304L and I installed a custom ROM on it a few months ago. Everything was working perfectly except for some bugs and some specific apps crashing. So I thought of flashing the stock firmware to go back to the original ROM. I didn't take a backup when I installed the ROM. I used Lenovo's "Rescue and Smart assistant' to download and flash the right firmware for my tablet. I was able to flash it successfully and all but when I tried to boot it up. It was just stuck on the Lenovo screen for a minute or two and then turned off. I tried turning it on several times but every time it would turn off after staying on the 'Lenovo screen' for a minute or two. I even tried booting into the (stock) recovery and factory resetting it and also formatting the cache partition but nothing worked. I also noticed that the device's bootloader is locked and the TWRP recovery got removed. Now even if I want to flash a custom rom, I can't because to do so I need to turn on USB debugging and turn on OEM-unlock but I can't boot into the OS. I tried flashing in 2 times now but its always stuck on the boot screen. Please help me if there is anything I can do with this.
Thank you.
Device: Lenovo Tab 4 10 (TB-X304L)
Firmware Files u can goto this link and download the firmware. steps are given in the comments. I always download from here
So I have this Lenovo Tab 4 10 (TB-X304L) and what I did was that I installed a custom ROM from this. It worked fine until that where it started to randomly shut down and when I turned it back on it would just be stuck on the logo. Re-flashed the whole ROM 2 times but didn't work. So I tried to flash the stock firmware it came with and learned that I need different tools to do so. So instead I used Lenovo's Rescue and Smart Assistant (LMSA) to flash the stock firmware. I put all the correct stuff (like model number and all) and started flashing through the app. Successfully flashed but the tab didn't turn on. So I entered into Fastboot mode and realized that the bootloader was now locked and the TWRP I had was also removed. After entering into FastBoot mode, I entered into the stock recovery and did a factory reset. After a few power offs/ons it finally turned on but would shutdown after 7 secs into the setup. Even if I didn't touch anything it would turn off.(even tried safe mode but it would still turn off) So I used the tool to flash it one more time and this time it would just get stuck on the Lenovo Screen for a min and then turn off. I tried flashing the firmware once more but its the same. Also it doesn't turn off when its in Fastboot mode or in the Recovery.
Now my situation is
>Can't get into OS
>Bootloader is locked
>No TWRP
>Can boot into Fast boot and stock recovery
>Don't know wtf to do at this point
I would appreciate if someone could help me.
Electron.48 said:
Firmware Files u can goto this link and download the firmware. steps are given in the comments. I always download from here
Click to expand...
Click to collapse
I'm trying to do this and I keep getting the following error when I try to download it
Sorry, you can't view or download this file at this time.
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.
Click to expand...
Click to collapse
Related
I rooted the tablet and it updated fine. I then reboot it and it is now stuck in boot loop. It says bootloader version unknown when I press power and volume button. What do I do?
Update. I have been able to successfully make my tab bootloop three times and three times have brought it back to life. All three times it has been because of an app that I guess is not compatible with 3.1. Because of my low thread post count I can't provide links or post into the development forum but my method has worked all 3 times.
A little background. First time I hadn't changed recovery and it was a bit easier. Second and third times I had cwm recovery and it was harder because adb wasn't recognizing my tablet.
First you need to have adb installed into your computer. I installed the sdk and then added the adb option. I then went into this post in the development forum: Re: [Solution] HC 3.1 OTA Difficulties 13% + Stock ODIN. In that post you'll find the Odin application for your computer and the appropriate PDA file for your tab. The PDA file contains the stock recovery, bootloader, and rom.
Whether you have stock recovery or cwm the next instructions are the same.
1. Connect the tab to computer.
2. Holding power button and volume down button, get into screen where you can choose fastboot or download mode. Choose download mode.
3. Once in download mode, on your computer open the Odin application.
4. Where it says PDA file, click the browse option to look for the PDA file you downloaded. Open it and it will be listed in the PDA section. Also the box next to PDA will be checked. Don't change any other settings.
5. Now you can press the button to run Odin. Don't touch tablet until it's done.
6. Now you can try rebooting it but it will still bootloop. Difference now is that you can adb into it.
7. With tab connected, go into cmd mode on your computer and type: adb reboot recovery
8. The tablet should reboot into stock recovery. From there wipe data and cache.
9. Reboot tablet and it should work! The tablet will be reverted back to 3.0.1. Just run the update again and enjoy.
Couple of notes. I tried the fastboot method mentioned in some posts but it never worked for me. This method that I've done has been flawless for me. I do have I/O version so I'm not sure if it is different from retail version. I think bootloops occur because some apps are not ready, stable, or compatible with 3.1. Something in the bootloader and recovery has changed in 3.1, whether it is changed via the apps or the update itself I'm not sure. I do know that the problem apps work great in 3.0.1, never causing bootloops, thus my conclusions.
Same thing happened to me. Fastboot -w did the trick. It wipes the tablet though.
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Help needed Samsung galaxy tab 10.1 stuck in boot loop
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
saviressej said:
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
How did you ADB it while it was in a bootloop?..
I'm stuck with this same issue! Everything was fine, I was on version 3.1 and I had rebooted it several times. Then one time it just got stuck on a bootloop and I can't figure out how to fix it. This is the google i/o version and I haven't done anything to it other than update to version 3.1.
I've been googling for an hour or so, but I have no idea what i'm suppose to be looking for. =\
you can recover.
i have posted detailed instructions in the OTA thread on xda.
sramasub said:
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
Click to expand...
Click to collapse
+1, i have the same problem. drained battery, recharged, stuck in boot loop. also got the "entering upload mode; cause undefined" message too.
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
_avatar said:
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
Click to expand...
Click to collapse
Yeah, I found your post a couple days ago, but couldn't get it to work. Once plugged into the wall charger, I couldn't get the charging icon to show up. I've tapped the power button, held it down for half a second, a full second, several seconds... it either does nothing, or tries to boot up.
I was able to get into Odin3 download mode and flash a ROM (see this thread: http://forum.xda-developers.com/showthread.php?t=1130216#2), but now my USB doesn't work and adb won't recognize it, so as a development device it's not very useful to me. I can't seem to get into the bootloader so I can't flash with adb or fastboot (when I boot into USB mode, adb doesn't recognize the device). I need to figure out how to flash an original I/O image, but can't seem to figure it out...
I've also had some difficulty getting to the "charging" screen, the trick is to be patient. Make sure the device is really off, plug it in, and walk away for a good while -- like 5 minutes.
When you say you're able to get it into USB mode what does that mean? Sounds like you are actually able to get it into fastboot mode. What operating system are you running? On my Mac the fastboot binaries I found floating around the net didn't work, I had to compile one from source. If you're able to get into fastboot mode but it's not detecting your device, and you have a Mac, I can send you the version I compiled from AOSP and you can try that. Let me know...
Try this...
http://forum.xda-developers.com/showthread.php?p=14791689#post14791689
Works for this guys.
I have a solution for the bootloop in my first post.
Sent from my GT-P7510 using XDA Premium App
I had a similar problem. Looks like Clockwork recovery can sometimes trash your /data partition and its format/wipe option won't fix it. I recovered by booting into stock recovery and formatting /data from there. Be forewarned that you'll lose your "sdcard," which really lives on /data.
Nice guide, thanks!
Ok so I was on a note 4/5 hybrid ROM and wanted to update to the latest stock unrooted ROM. Well it started off rough. I wiped it then tried to install QB3 via Odin but it didn't take so then I was stuck on download mode. I managed to get out of it by installing an OK1 ROM. I think that was the base of the hybrid ROM that I was on. That took and then I just used smart switch to update to the latest ROM and it worked. I tried to install TWRP via Odin but it doesn't take and I don't know why. Now every once in a while it will just turn off and I have to pull the battery out but then it goes to download mode. Sometimes I can reboot it and it will be fine. Other times it will go to download mode so I have to force it to boot into recovery. I select reboot system and then it goes back to download mode. I think the message at the top left of download mode says something about not being able to read mmc. Not sure what that means though. So it takes me several reboots going through the same process before it will finally boot normally. Has anyone else encountered this? I'd really like to get TWRP installed and root the phone but keep the ROM stock. I've tried installing a rooted stock ROM but it doesn't take. I don't know what else to do. Thanks in advance for any advice you guys have. If I don't reply it's because my phone rebooted and got stuck lol
If your getting the mmc message it's a bad sign. It usually means the board is going bad, it least that's what I've heard.
I actually found the cause of it. I had reactivation lock enabled so it wouldn't let me install TWRP or anything. Once I disabled it I was able to install TWRP and flash a rooted ROM. However it will still reboot at random times but it's not as much as before and it didn't get stuck in download mode.
I've spent all day fighting with the boot loop on my A500f.
I had the phone running really well with Ahmed's Resurrection Remix ROM on this post:
https://forum.xda-developers.com/sa...om-resurrection-remix-5-8-2-sm-a500h-t3572062
He doesn't detail TWRP installation, so I used DeadSquirrel's 3.1.0 post here:
https://forum.xda-developers.com/sa...overy-twrp-3-0-2-0-samsung-galaxy-a5-t3439233
I hadn't seen that TWRP can be installed without root, so I rooted with Chainfire first. I'm not sure, but I think I got the Chainfire file from this post:
https://forum.xda-developers.com/sa...-to-root-galaxy-a5-a500fu-lollipop-5-t3137613
The file I downloaded for the A500f is "CF-Auto-Root-a5lte-a5ltexx-sma500f.zip" (contains tar.md5)
The post says it is for Lollipop, but the instructions say this is a Chainfire root zip for Android 4.4.4. One post suggested this might be the cause of my boot loop.
The instructions say that this Chainfire Auto Root solution also contains a recovery file, but I was never able to boot into this recovery, so I went directly to installing DeadSquirrel's TWRP. I was able to boot into this recovery. From there I installed the Resurrection Remix ROM. WIthin the ROM, I installed SuperSU from the Play Store, but SuperSU informed me the phone was not rooted, so I flashed the SuperSU root zip from their website, which I believe was the file, A500FXXS1CQC2_A500FOJV1CPH3_XFE.zip
SuperSU now reported root was present, so I installed WiFi Connection Manager from the Play Store, granted it root access in SuperSU, and used the Fix Problems menu item to repair the wifi shutting off the phone problem that I was originally working on. That fix worked well, so I left the wifi on and ran YouTube on Autoplay for about 4 hours. Deciding the problem was solved, I gave the phone back to my son, and he brought it back to me dead 5 minutes later. I'm not sure if it already that the boot loop problem at that point.
The phone would no longer boot. I noticed a seandroid enforcing notification, and thought it might be a security issue preventing boot. I found a thread that said I needed that flashing back to a Samsung ROM would remove the seandroid notice and that I needed to update to Android 6.0.1 before installing TWRP to solve the boot loop issue. I went to Sammobile and found the newest ROM for my A500f was the A500FXXS1CQC2_A500FOJV1CPH3_A500FXXU1CPH2_HOME.
I installed this in Odin, and the phone has never come back to me since then. I've made endless retries throughout the day, trying different combinations of the Chainfire root, different versions of TWRP, and different root methods, but all to no avail. One post even suggested that if you flash factory ROM from Odin just once, it will create a boot loop, but if you flash twice, it solves it, but it didn't work for me. It's also gotten increasingly difficult to get into recovery. Whether in stock ROM or TWRP, I was only able to get in about 10% of the time. Boot loop behavior has varied between boot logo - vibration - black screen and battery charge logo - vibration - black screen.
I found this thread that is supposed to address the boot loop problem, and I tried these versions of root and TWRP, but it didn't help:
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a52015-sm-a500f-t3360802
At the moment, I'm on stock ROM. On power up, you get the Galaxy A5 screen, then it vibrates and goes black, then the lightening battery logo comes up, it vibrates, and goes black, and then the green battery status logo comes up, and then the phone goes black. It's also booting into stock recovery okay, and I can do the recovery functions. I just can't boot the phone.
So now, I try the instructions again in ashyx's TWRP post. Now I can get into TWRP. I power up and the phone sticks on the Galaxy A5 boot screen for a long time. Then it vibrates and repeats. It's basically the same as above, but there is a long delay before rebooting instead of instantly as before. Now I go back into TWRP and flash the Resurrection Remix ROM and the behavior is the same. Power up and get the Galaxy A5 boot screen for 8 seconds (this time sporting a warranty bit: kernal notice), 2 seconds of black screen, vibration, battery/lightening logo blinks on, then off, vibration, battery/lightening logo blinks on then off. Black screen, then standard battery charging percent indicator. I did that three or four times to make note of the behavior. Then the power switch wouldn't work, so I used the technique to press the volume up and down key together with the power key to turn it back on. Now it is in a non-stop 5 second cycle of vibrate - flash the icon - black screen that won't quit. Throughout the day I've been stuck with this in both stock and custom ROM. Only once during the day did I see the custom ROM boot all the way through. The stock ROM has never booted.
Now the recovery key combination won't boot TWRP either. The key combination just makes the Galaxy A5 screen flash instead of the battery icon. But I can get into TWRP by rebooting with the recovery key combination on leaving Download mode.
If anyone understands what's wrong here, I'd appreciate it.
Thanks
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Thank you. That did the trick. Going back to the original factory ROM of Android 5.0.1 brought the phone back to being bootable again. I wish I understood what is going on on the low level to cause these things!
MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Samsung Smart Switch what is it?
Faraz_74 said:
Samsung Smart Switch what is it?
Click to expand...
Click to collapse
Samsung app:
http://www.samsung.com/us/smart-switch/
Same Issue
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
I believe Sammobile is the standard location to download stock Samsung ROMS:
https://www.sammobile.com/firmwares/galaxy-a5/SM-A500F/
xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
you can download in here also updato.com
Sent from my SM-A500F using xda premium
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Renojjv said:
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Click to expand...
Click to collapse
Check my reply in this post
https://forum.xda-developers.com/android/help/softbricked-lava-r1s-please-help-t3730982
Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please