hi, iam new user of TF300t, i installed the Energy.TF201.or.TF300..JB.03.18.2013.( i dont remebmer is the STOCKED or THEMED) ! after that i wanted to install BAKED_TF300T_BB-8, but the device stay on the boot menu! so what i did , installed the 6.0.2.3 CWM ( [CWM][6.0.2.3 / 5.5.0.4] Official CWM Recovery for JB/ICS + ROOT) ! after that i rebooted the device. Stock in the Asus LOGO! After i rebboted by holding the power menu and volume down, i choosed the wipe option ( i dont know why) and from tht time, it rebbots only in the 6.0.2.3 CWM what ever i do!
For 5 days, i have tried to flash via fastboot twrp.blob, i have pushed the firmware from asus to /sdcard and flashed via fastboot always, i have tried and read similaire problems! didt succed! i have always the message tht Can not mount sdcard! cant mound E/data! cant mount anythingg!! What ever i do, always reboot to this CWM !!!!!
please any one help me!!!!!!! thanks a lot!!!
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
sbdags said:
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
Click to expand...
Click to collapse
but i can use adb commands, and fastboot commande ( except tht i have waiting for device each time) so its bricked for EVER?!
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
sbdags said:
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
Click to expand...
Click to collapse
yes, it accept nothing! even if i downgrade to ics to apply the nvflash its worse! so should i say bye forever to my tf300t?!! if yes, which tablets tht cn be less bricked than others? thks a lottt! wht would u do if u were at my place? thksssssssssss
buy a new mainboard (motherboard)
Sent from my TF300T using xda app-developers app
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Ti2 said:
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Click to expand...
Click to collapse
thanks for yr reply ill try even im bricked! ill by another tabelt but not asus, maybe samsung, i have a GS2 , i install every thing without problem, i think there tables dont brick easly! true?
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Ti2 said:
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Click to expand...
Click to collapse
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
Wrong? No.
Harsh? Yes.
Read read read. Learn learn learn. Then read some more. When unsure, ask questions. Don't just try, then read the manual tot learn how you screwed up...
I am unsure tot flash 4.1 bootloader based roms through the 4.2 patched TWRP. I am NOT just going to try, I am awaiting an answer for 3 days now.
Is a Tab(2) as easily to brick as a Transformer? Yes it is.
sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
true wht u said !
Not trying to be harsh but that's why they call it "bleeding edge". You take the risks if you cannot be patient.
Sent from my SCH-I510 using xda app-developers app
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
lk2l said:
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
Click to expand...
Click to collapse
no succes to flash anything! always back to cwm 6.0.2.3...
when you type fastboot devices or adb devices can you see the device?
lk2l said:
when you type fastboot devices or adb devices can you see the device?
Click to expand...
Click to collapse
i can see this 0123456789ABCDEF, thts not the device name sure! isn't ? i can flash via fastboot ( sending ok, flashing ok) i flashed the blob file tht comes with the Asus frimwork 10.6.1.8 but nothing, always i go back to the 6.0.2.3 CWM! i flashed the twrp.blob file! same thing! im turning in an empty circle! good for trash??
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
lk2l said:
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
Click to expand...
Click to collapse
hope so! thkssssssssssssssssssssss
can you tell me which procedure you do to flash the recovery?
here you can found all I have used to flash my tf300t with the bootloader 4.2.1
fastboot+twrp recovery 2.4.4.0-4.2
is possible your fastboot dosen't work correctly?
Related
hey need some help have succesfully rooted my phone but after flashing trickdroid rom my phone got stuck on the white htc screen.. i believe i have since wiped everything.. i now get unable to mount sd card messages and waiting for device messages when ever i now try do anything including flashing a stock rom. i have tried using the all in one tool and i re locked my bootloader through it but now cant re unlock it.. i can use the tool to reboot my phone into bootloader and recovery modes.. but not to do any sort of flashing, have read numerous posts and threads but no luck. Please help
nj_mills said:
hey need some help have succesfully rooted my phone but after flashing trickdroid rom my phone got stuck on the white htc screen.. i believe i have since wiped everything.. i now get unable to mount sd card messages and waiting for device messages when ever i now try do anything including flashing a stock rom. i have tried using the all in one tool and i re locked my bootloader through it but now cant re unlock it.. i can use the tool to reboot my phone into bootloader and recovery modes.. but not to do any sort of flashing, have read numerous posts and threads but no luck. Please help
Click to expand...
Click to collapse
Are you using TWRP or CWM as your recovery?
twrp
You will not be able to flash any custom roms as long as your bootloader is locked. The most you can do with the locked bootloader is use an RUU to get back to stock. Which bootloader are you on now? 1.14?
my bootloader is unlocked at this moment. um would my bootloader be where it says.. hboot? if so its 2.13.0000?
Correct, the bootloader is an all white screen, with the radio, hboot and other such info at the top of it. Well you are good then. Just so we are clear you have a HTC One S S4 right, you dont have a HTC One S C2? Thats very important that we get that info correct, we don't want to brick your device.
im almost certain its a s4.. i got it from t mobile here in the uk any check i can do from the bootloader to confirm?
If you're not S-off, did you make sure to fastboot flash the kernel after flashing rom in recovery?
From my Evo LTE, yup.
im s-on, and no i dont believe i did no
how would i go about fixing that?
nj_mills said:
im s-on, and no i dont believe i did no
Click to expand...
Click to collapse
You should have read and followed the instructions in the OP of the rom you downloaded so.
Try flashing boot.img in fastboot mode with typing 'fastboot flash boot boot.img' in terminal window. Hope you're familiar with the platform-tools in android development kit...
Else download here and
follow the step by step instructions.
reboot into bootloader with your phone connected to you pc. make sure you are in Fasboot USB mode, it should say that in the bootloader screen. Move the boot.img from whatever rom you flashed and put it in the same directory as ADB and Fastboot. make sure its named boot.img. open a command prompt that points at that same directory as ADB and Fastboot, type
fasboot flash boot boot.img
Click to expand...
Click to collapse
and after its done type
fasboot erase cache
Click to expand...
Click to collapse
have tried that and still get stuck on the white htc screen saying this build is for development purposes....
thanks for trying so far
Is it still locked? And you're on custom recovery (twrp)?
You need to reflash the ROM you want. Then reboot into the boot loader from TWRP. Once there, follow my previous instructions.
Sent from my One S using xda app-developers app
it says unlocked at the top of the bootloader screen... and i have twrp installed yes
nj_mills said:
it says unlocked at the top of the bootloader screen... and i have twrp installed yes
Click to expand...
Click to collapse
Thats's already half the way. Please do what impostle says (reflash, reboot, etc.)
how can i get the rom onto my phone now that i cant access the phones internal folders?
Is the ROM not on your phone anymore? If not, just mount from TWRP and copy over.
Sent from my One S using xda app-developers app
---------- Post added at 01:45 PM ---------- Previous post was at 01:42 PM ----------
You guys need to start reading the whole guide before rooting and flashing.
Sent from my One S using xda app-developers app
twrp - mount - mount usb storage
Then copy that file to root or wherever you want.
Which TD version do you have?
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03
matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD
i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows
Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.
EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?
http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you
sorry guys today i was very busy, i'll try to solve it tomorrow
matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem
I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.
pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news
matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD
i'll definitely try that method! i'll let you know, thanks guys
matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....
I have an Asus TF300T that I have unlocked, and flashed TWRP 10.6.3.1 onto it. I have then flashed the latest 4.4 Cyanogen nightly, and it bootloops. I think this is because of my bootloader.
Normally once I am at the custom recovery point on a device, I have no further issues and flash rom's like crazy. This specific bootloader requirement is new to me. I've farted around on a few devices before (Moto Milestone, HTC Desire Z, HP Touchpad, Sam GS3), but I'm not very technical.
I think my current bootloader is 10.4.2.18. (It reads Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.18-20121122" A03).
How do I upgrade my bootloader to allow for 4.4 rom's, and must I downgrade my bootloader if I want to install something like Ubuntu?
The instructions mentioned here http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7 took me to http://forum.xda-developers.com/showthread.php?p=49258989 but neither of these post's seem to be talking about the bootloader. Is there a way to simply upgrade just the bootloader? Or must I flash a special stock Asus rom that upgrades it for me, then reflash TWRP and proceed from there?
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
jiddahidda said:
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
Click to expand...
Click to collapse
Use fastboot to install the latest stock blob. Remember to extract the blob file:
Code:
fastboot -i 0x0B05 flash system blob.blob
Then you can flash TWRP 2.6.3.2 and then a KitKat ROM.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
cmendonc2 said:
Code:
fastboot -i 0x0B05 flash system blob.blob
Click to expand...
Click to collapse
Is there another way to get it into fastboot mode? See my post above this one.
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
jiddahidda said:
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
Click to expand...
Click to collapse
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
Click to expand...
Click to collapse
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
cmendonc2 said:
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
Click to expand...
Click to collapse
I think I know the answer, but I'll ask anyway. Is it possible to use someone elses NvFlash backups? I looked into making these backups but never did it .
cmendonc2 said:
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
Click to expand...
Click to collapse
I've seen you suggest this script several times in several threads, but could never find it. I've been searching for threads with the word Buster or Recovery or Script and I can't find anything that seem's to be what you're talking about? Sorry to be a pain, what's his XDA username?
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
jiddahidda said:
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Yes, but did you try using the paper clip to reset it? try a few combinations of using it.
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it