Related
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
Good day everyone,
Thanks for taking the time to read this. I am in desperate need of your help. I recently purchased a HTC One S from an online store they told me it was new never used locked phone. Turns out phone was rooted, 4g does not work, and it could not recognize e drive, (internal sd card)
After reading the all in one i re-rooted it and install the teamwin version of recovery.
Now i never had any back ups or any factory files. as i got the phone rooted with software that did not work. My phone now has no rom and i cannot install from adb sideloader, or an other means. I am new to this and cannot seem to figure out how to get my phone back to even stock un-rooted etc. I tried multiple forums and download links but nothing.
i was able to install vipers rom at one point but despite several attempts to reinstall. recovery does not see files loaded. which i can see on my mac or pc.
the other strange thing i notice is that at the top in fastboot mode i sometimes see unlocked in pink only and other times i see both unlocked and tampered. when its unlock only none of my computers recognize connection.
I also tried boot.img for flash. The furthest my screen no goes is the htc logo, then goes black.
Please help, even to just point me in rite direction to have this resolved.
the boot.img, did you flash it via fastboot? (fastboot flash boot boot.img)
And, one question that comes to mind... they sold you a device as new, yet it wasnt.. Why didnt you return it?
Goatshocker said:
the boot.img, did you flash it via fastboot? (fastboot flash boot boot.img)
And, one question that comes to mind... they sold you a device as new, yet it wasnt.. Why didnt you return it?
Click to expand...
Click to collapse
Yes I tried several times loading the boot.img via fastboot.
As far as returning the device i trashed the mailing box but kept original packaging so no return address. I called the company which i made the purchase from "N1wireless" several times and sent several emails to them. They have yet to reply or answer any of my calls. Which is why I am so frustrated.
mnitllc said:
Yes I tried several times loading the boot.img via fastboot.
As far as returning the device i trashed the mailing box but kept original packaging so no return address. I called the company which i made the purchase from "N1wireless" several times and sent several emails to them. They have yet to reply or answer any of my calls. Which is why I am so frustrated.
Click to expand...
Click to collapse
Boot into recovery, select mount > mount usb storage. From pc move the Rom.zip to your sd card which should now be showing on your pc. After it is moved to your phone select unmount then press home button in twrp recovery. Then install the Rom. After install open up adb and type adb reboot bootloader then press enter. Now fastboot flash the boot img from inside the Rom.zip on your computer. After that reboot your phone and report back
Sent from my HTC One S using xda premium
bochocinco23 said:
Boot into recovery, select mount > mount usb storage. From pc move the Rom.zip to your sd card which should now be showing on your pc. After it is moved to your phone select unmount then press home button in twrp recovery. Then install the Rom. After install open up adb and type adb reboot bootloader then press enter. Now fastboot flash the boot img from inside the Rom.zip on your computer. After that reboot your phone and report back
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Hi, thanks for the reply, thats just the thing I cannot in recovery install any rom loaded to sd card. It fails. I tried reinstalling the recovery and it still not reading my sd card.
So my guess is i need a new twrc or how to do it from my mac, as now when i try on my pc it is failing as-well. Once I get the recovery to work I will try your other suggestions as I think it will work based on the steps you mentioned.
I am trying to figure out how to use terminal to reinstall recovery. any suggestions or links will be greatly appreciated.:good:
you install recoveries through fastboot, fastboot flash recovery recovery.img
Goatshocker said:
you install recoveries through fastboot, fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I reinstalled recovery several times now and it wont recognize the sd card. is there another recovery i can download and use? Also is there any instructions for a newby to use terminal to re-boot, everything from scratch. Meaning if the phone is completely blank except the fast boot and a recovery manager no backups or stock kernel etc. what is the format to be used in order for the computer and recovery to recognize the sd card?
I think I need a good recovery rom like cmod if there is one for the htc one s or the stock one if someone has it.
hi i had that problem
mnitllc said:
I reinstalled recovery several times now and it wont recognize the sd card. is there another recovery i can download and use? Also is there any instructions for a newby to use terminal to re-boot, everything from scratch. Meaning if the phone is completely blank except the fast boot and a recovery manager no backups or stock kernel etc. what is the format to be used in order for the computer and recovery to recognize the sd card?
I think I need a good recovery rom like cmod if there is one for the htc one s or the stock one if someone has it.
Click to expand...
Click to collapse
I had that problem the sd card would not be seen by my laptop and the phone would not boot at all if you plug in the phone to your go to start and then computer right click on your c drive go to manage and see if you can see it there if so try to format it and then reboot the phone if it works you can then install cwm as a recovery system then you can put what rom you wont on it i am use in zenRom 1.05 and to me its the best coz it like the htc rom that the phone come with if that don`t work let me know coz i have more tricks to try i hope this helps you out.
Theres only TWRP and CWM for the S afaik, and CWM sucks. TWRP is the one to use.
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
violentlighting said:
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
Click to expand...
Click to collapse
got it. will try it asap.
I could not get the stock recovery via that link you provided. If there is another link to the stock I would appreciate it. I had to flash it wit cwm twice then reflash with twrc to get it to identify the sd card. i had tried the viper rom but my 4g and wifi doesnt work. Will try trickmod hopefully that works with no more issues
violentlighting said:
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
Click to expand...
Click to collapse
Hey thanks allot for your suggestions. I made some progress. It kinda worked. However I my wifi and data connections no good. I tried the 9.1 update and then tried the tweaks.
Do you know if it is possible to get stock kernel and stock rome to undo changes on device?
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
philos64 said:
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
Click to expand...
Click to collapse
sorry for the delay - thanks for the reply.
I dont know how to tell if im rooted from recovery.
So just went ahead and flashed the root file i found here:
http://www.androidgadgematic.com/2012/10/root-asus-transformer-pad-tf300-install-cwm.html
flashed Baked 7 and gapps again with same result.
(however i noticed at first reboot the asus screen shows a quick blue loading bar under center logo. then nothing.)
rebooted into TWRP - wiped - flashed root.zip again - restored backup.......asus screen.
another thing i noticed was when i try to install (flash) anything, it says no md5 found or if i select "force md5 check" it fails.
im a seasoned novice. I've gotten myself out of some sticky jams. but im totally lost here....
cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
tobdaryl said:
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
Click to expand...
Click to collapse
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
cavz903 said:
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
Click to expand...
Click to collapse
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
philos64 said:
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
Click to expand...
Click to collapse
ok so, downloaded WW stock firmware from Asus site. flashed blob file via fastboot.
it said it finished "okay"
rebooted and, back at the Asus Screen.
and now i dont have recovery either. any suggestions?
thank you
any other ideas? im lost here... thanks
cavz903 said:
any other ideas? im lost here... thanks
Click to expand...
Click to collapse
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
tobdaryl said:
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
Click to expand...
Click to collapse
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
Flash the latest twrp (2.4.1.0). There were issues of using 4.2 and custom recoveries. That was the reason for the last two versions of twrp.
All custom roms here I have checked are pre rooted so the only time I flash root is with a stock rom.
If you were not already using twrp 2.4.1.0 then reflash your stock rom. Earlier versions might not flash the roms properly for 4.2. We need to get working first then you can flash your rom choice.
I hope your version of twrp is less than 2.4.1.0 because if not I'm lost at the moment. I'll be thinking and searching while you play.
Good Luck!
Note: Sorry I should have said twrp 2.4.1.0 JellyBean!
cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
flukeSG2 said:
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
Click to expand...
Click to collapse
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
tobdaryl said:
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
Click to expand...
Click to collapse
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
flukeSG2 said:
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Since you did not provide data about your situation I looked at your previous posts. Notice the big red line in my signature about WIPE DATA.
I'll try to help but this is a hard one to fix. You have to be willing to keep chipping away till I give or we have success. It can be very frustrating.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
Click to expand...
Click to collapse
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
tobdaryl said:
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
Click to expand...
Click to collapse
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
flukeSG2 said:
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
Click to expand...
Click to collapse
Good. While waiting you can download the latest ICS stock 9.4.3.30. You will find it in post 3 of this thread.
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
flukeSG2 said:
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
Click to expand...
Click to collapse
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
tobdaryl said:
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
Click to expand...
Click to collapse
It's not charging fast enough on my pc, so I had to disconnect it and plug it into the wall for awhile again. I can pm you if you'd like when I get it fully charged.
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
you need to root the device and use flashtool by androxyde(Easier and user friendly), first download the rom and put it in internal/external memory and then install thunderzap 4.12 by select bootkk.img and install it in fastboot mode in flashtool, now enter the recovery go into wipe and format options and choose clean to install a new ROM and then flash the pac rom and reboot
Root isn't necessary.
Download PAC ROM, Take boot.img inside the zip.
Flash boot.img via fastboot.
Boot into recovery, wipe data / factory reset.
Flash ROM and GApps.
That's it
NOP, you dont need to root to install a custom rom
felix leiter said:
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
Click to expand...
Click to collapse
you can download the rom, extract it and keep, boot.img file, in fastboot folder, and also keep the downloaded rom zip file in sd card for later use.
than you can use use fastboot commands to flash those boot.img which will install the recovery into your phone, than .
use reboot command in fastboot, it will reboot your phone, take out your cable, using volume up key go to recovery,
there clear all the cache and delvik cache file, then, install your custom rom by selecting from your sd card, it will take a bit of time for first time, so don't worry,
than you are done,