hey guys i just reverted back to stock from cm12.1 and after that my mobile is automatically booting to recovery and not booting sytem at all... But if i flash recovery with boot.img i can boot successfully... may i know the reason please.......
something probably went wrong with the boot.img flashing it to the boot partition. just do a full fastboot factory flash and you should be fine.
You should try flashing to complete stock using this guide. If you want to keep your data, ignore this line:
Code:
fastboot erase userdata
.
Same problem here, the phone starts on fastboot mode every time i turn off and turn on. My is XT1543, any help?? I got my bootloader relocked.
I found the solution for my device. Installed the Stock Rom on RSD Lite v6.2.4 and works here. Boot up into system, no more boot on Fastboot at startup. Vefore I was doing the flash over ADB commands, I think the bug was there. RSD Lite fixed it.
I have made a program recently which fully wipes the phones internal memory, and reflashes the partition table. This would fix your problem most definitely.
Il be uploading the work to my onedrive tomorrow but I cant right now as it is on my work pc which I wont have access to til tomorrow
If anyone wants the program, email me at [email protected] if you really need it now and I will reply with the file attached to it, all it means is that I have to spend 20 minutes on a slow remote desktop to retrieve the file. But I'm happy to do that if that is what makes the members of XDA happier be aware you need python 3.4 installed for it to work!
I hope this is a working solution for anyone that needs my program !
Related
So i have been trying to fix my phone now for about.... 5 days or so.
I know that its the internal partitions because nothing I MEAN NOTHING has fixed it.
Flashed everything to stock flashed every recovery IMG and everything else under the sun. The problem is that the phone is stuck in a reboot loop. I ran an RUU into the phone by use of good old cmd. Had to access it through fastboot menu.
I have no ADB!! I am stuck in Hboot and Fastboot menu. I cant get into anything else and i cant fix anything else. I have to fix the partitions first, This is an advance problem so i really need some professional help here.
IE how the F*ck do i fix this >_<
TestTodeath said:
So i have been trying to fix my phone now for about.... 5 days or so.
I know that its the internal partitions because nothing I MEAN NOTHING has fixed it.
Flashed everything to stock flashed every recovery IMG and everything else under the sun. The problem is that the phone is stuck in a reboot loop. I ran an RUU into the phone by use of good old cmd. Had to access it through fastboot menu.
I have no ADB!! I am stuck in Hboot and Fastboot menu. I cant get into anything else and i cant fix anything else. I have to fix the partitions first, This is an advance problem so i really need some professional help here.
IE how the F*ck do i fix this >_<
Click to expand...
Click to collapse
Did you try to mess with the partition addresses?
You can always do 2 things:
- do a fastboot boot recovery.img
try to mount the partitions from there; see if they mount at all
or list your mtd partitions (The DI is on MTD right?)
- do a fastboot boot boot.img
and post a logcat to pastebin
Remote not allowed
Did you try to mess with the partition addresses?
You can always do 2 things:
- do a fastboot boot recovery.img
try to mount the partitions from there; see if they mount at all
or list your mtd partitions (The DI is on MTD right?)
- do a fastboot boot boot.img
and post a logcat to pastebin
Click to expand...
Click to collapse
Well im running all stock so every time i try to run a fastboot command it returns as Remote not allowed. Heh Im pretty sure im NOT running a perfected SPL.
Any way to fix the remote not allowed?
Ps im not to smart lol clarify DI=what? MTD=what? logcat to pastebin? what? sorry Im not to to firmiluar with every term
PPs google chrome's spell check sucks -_-
Ok so i need to enable fastboot from the phone. there is an ENG HBOOT that runs .77 but i got a black screen which im guessing means i have an SLCD. SO how do i enable it :/
Good news and bad news. I got to run fastboot commands to the phone but i flashed the recovery partition with stock and CWM 3.0.0.5 and 3.0.0.8
No good :/
Seems like i have to erase every partition and format everything. the ram space; i mean everything. i have to treat this like the company sent me a blank phone and i have to put everything on it. Any help?
Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.
So I forgot and did a dirty flash to the final version of Lollipop without wiping data. I should have moved my data over but now I'm stuck with a black screen and a back arrow once I boot up the OS.
I know that in order to fix this, I need to flash again and do a full wipe, however, I need to get my files (pics and music) off the phone. I am unable to put a custom recovery on the phone. When I flash TWRP to the phone, it says it succeeded but then I just get the open android with the red thing on it when I try to go to recovery mode.
I've tried adb pull in fastboot mode, but I am unable to get my computer to recognize my device in fastboot mode through adb (fastboot works of course).
When I've booted up, my lock is on the phone so I cannot use adb to pull files without getting into the OS (which is impossible at this point).
I'm running out of ideas on how to get the files, but I'm sure that someone here must have run into the same issue.
Any assistance would be appreciated.
wangkomi said:
So I forgot and did a dirty flash to the final version of Lollipop without wiping data. I should have moved my data over but now I'm stuck with a black screen and a back arrow once I boot up the OS.
I know that in order to fix this, I need to flash again and do a full wipe, however, I need to get my files (pics and music) off the phone. I am unable to put a custom recovery on the phone. When I flash TWRP to the phone, it says it succeeded but then I just get the open android with the red thing on it when I try to go to recovery mode.
I've tried adb pull in fastboot mode, but I am unable to get my computer to recognize my device in fastboot mode through adb (fastboot works of course).
When I've booted up, my lock is on the phone so I cannot use adb to pull files without getting into the OS (which is impossible at this point).
I'm running out of ideas on how to get the files, but I'm sure that someone here must have run into the same issue.
Any assistance would be appreciated.
Click to expand...
Click to collapse
theres no adb in the bootloader, just fastboot.
i dirty flashed from kitkat(rastakat rom) to lollipop, didnt have any issues at all. what did you dirty flash from? you could just flash the factory img via fastboot, but not flash the userdata.img, which would let you keep your data.
When you're in bootloader and try to flash TWRP (try the latest), make sure you hit reboot bootloader to see if that helps.
I went from the last pre-release to the official release. of lollipop.
I'm going to try twrp again see what I get.
Thanks
wangkomi said:
I went from the last pre-release to the official release. of lollipop.
I'm going to try twrp again see what I get.
Thanks
Click to expand...
Click to collapse
somebody posted a thread today about how to dirty flash from the preview to lollipop. it appears normally you cant.
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.
Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.
Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk
This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more
Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0
No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.
So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?
Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck
Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?
Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.
For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....