Related
hi all,
Firstly apologies if this is covered somewhere but for the life of me I cannot get to the bottom of this. I have spent 2 weeks on and off trying to get a solution but my Sensation is still boot looping.
The problem occurred when I turned on the camera but was faced with a blank screen. I could return to home screen but the camera would not work each time I launched. So I rebooted the device but then I was stuck in this boot loop.
Device info
HTC Sensation S-OFF RL
HBOOT-1.27.0000
RADIO-11.21.3504.13_2
I was running Insert Coin 2.3.5 ROM for some time without issue
I was hoping I could just do a superwipe and flash a new ROM
FAIL - each time I boot into CWM and select Recovery, it just goes back to bootloop.
I selected Factory Rest from CWM menu
FAIL - it just goes into bootloop
Also cannot use ADB as the device will not connect to the PC. Im using a card reader to put files on the SD card but have not being successful resolving the issue.
Tried an SD card from a stock Sensation, no difference. Booting with no SIM, not working.
Most Bootloop fix's seem to involve super wipes / flashing new ROMs but because my Recovery goes into the bootloop I dont have this option. I wish it was so easy.
Can anybody offer an other ideas.
Thanks for you patience, I am not much of a modder or Android expert. I had just flashed a ROM many months ago to help improve battery life and I was happy with that.
Have you tried re-installing your recovery throught the bootloader?
try different recovery (4EXT) or reinstall recovery again
thanks guys.
I found these flashable recovery files. Both CWM and 4EXT. I have tried both zips and ran the update in HBOOT but am still booting in CWM and if I select RECOVERY is goes too bootloop again.
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
I think I might just give up and drop the phone into a phone repair shop and let them try it.
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Try this pg58img (it helped me)http://www.wuala.com/LuckyThirteen/Elegancia/Official RUU Sensation/ it will update your sensation to ICS, (you will maintain s-off)
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
GROGG88 said:
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
markmcie said:
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
Click to expand...
Click to collapse
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
If you can boot normally into ICS and you are rooted, then get the 4Ext app or the ROM Manager app and flash the recovery through one of those.
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
Ill do this a few times over the weekend and hopefully I can get up and running again. I will let you know how I get on.
Thanks
markmcie said:
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
Click to expand...
Click to collapse
Well I'd have to agree with dublinz then...
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
markmcie said:
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
Click to expand...
Click to collapse
Flashing the ICS PG58IMG.zip doesn't replace the recovery.
Fix recovery first. Use stock recovery. When you get that working, change to "simple" cwm recovery.
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
before flashing stock recovery...can you try this first
get this recovery image
and flash the recovery via fastboot
steps:
1.go to fastboot in your device and connect it to your pc (after this device should read fastboot usb)
2.get the adb/fastboot setup ready guide here
3.go to your adb folder and place the downloaded recovery.img there
4.type fastboot devices (it should show your device serial number)
5.now to flash type
fastboot flash recovery recovery.img
this should do...if it didnt work then let me know ASAP...then we'll think of other solutions
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
EddyOS has them , search that. I'll try to locate them.
I remembered incorrectly, it was only CWM and 4EXt
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
But you can find stock recovery in this forum:
http://www.htcsensationforum.com/ht...ota-update-on-rooted-phone/msg76452/#msg76452
scroll down a little bit ...
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
Here you go:
http://db.tt/kvTvDblW
It should include all MID's and most CID's that I know of...
GROGG88 said:
Here you go:
http://db.tt/3YSslZVg
It should include all MID's and most CID's that I know of...
Click to expand...
Click to collapse
Link is doing a 404 ...
SanityPreservation said:
Link is doing a 404 ...
Click to expand...
Click to collapse
Fixed...
If anybody need recovery, full worked with new 4.1.1 JB get it here.
Moderator Edit:
Link removed as it is proven this recovery can damage your device.
Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
pawitp said:
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Moscow Desire said:
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Click to expand...
Click to collapse
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
this one save´d my TAB!!!
i was able to reanimate it after i messed up ..
THX a lot
pawitp said:
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Click to expand...
Click to collapse
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Gigabyte0 said:
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
You should give some info when posting, otherwise it is "unknown".
The boot.img contains the kernel not the bootloader. The kernel source is yet to be released by Acer and we don't know if Acer has blocked the dangerous emmc wipe command (which will randomly brick tablets, the more you wipe, the riskier you are) like I did on my kernel or not.
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
But what it does not, it does not flashes. Freezes and hangs. Have my tab after 30 minutes. removed and restarted, now it hangs in APX mode. Do you have a solution for this?
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
meier2009 said:
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
Click to expand...
Click to collapse
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
Click to expand...
Click to collapse
Yes, it meant the version of Gigabyte0. Does not sound good.
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
NoThrills said:
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
Click to expand...
Click to collapse
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Moscow Desire said:
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Click to expand...
Click to collapse
Maybe you can also let this know on 4PDA.ru, as I am not Russian (and you are) you can probably explain it better:
In the Acer 3.0 Android kernel the command MMC_CAP_ERASE, which has caused all the old bricks, is still present. At least it is in the A110 3.0 kernelsource and I have no reason to believe they would remove it in the A700 3.0 kernelsource but not in the A110 one.
When this command exists in the kernel, and the Recovery also allows it (Recovery can also disable it, but the current A700 recovery doesn't do that), you are almost guarantueed a brick.
If you could translate that to 'the Russians' I guess we can save a few more people from bricking.
Thread Closed
So i guess I felt out of date and wanted to root my phone and use that cm10 rom or whatever everyone else is and i messed it up real bad. I keep getting this msg "this build is for development purposes only do not distribute outside of htc.." on the loading screen. At this point i just want to restore it back to normal , idc if i lose data , i just want my phone to WORK! I've flashed a clean recovery.img but whenever i try to access recovery , it brings me back to that screen with the red words. In addition , my phone is rogers so i can't even find a correct RUU to install. Does anyone have any suggestions as to how I can get my phone to work again ? Any help is greatly welcomed !
P.S Wow i think it got worse , now it doesnt even loop again , it goes start into that menu bootloader, reboot , power down.. Omg i spent 5 hours looking into this. I NEED HELP!
Lasts3cond said:
So i guess I felt out of date and wanted to root my phone and use that cm10 rom or whatever everyone else is and i messed it up real bad. I keep getting this msg "this build is for development purposes only do not distribute outside of htc.." on the loading screen. At this point i just want to restore it back to normal , idc if i lose data , i just want my phone to WORK! I've flashed a clean recovery.img but whenever i try to access recovery , it brings me back to that screen with the red words. In addition , my phone is rogers so i can't even find a correct RUU to install. Does anyone have any suggestions as to how I can get my phone to work again ? Any help is greatly welcomed !
P.S Wow i think it got worse , now it doesnt even loop again , it goes start into that menu bootloader, reboot , power down.. Omg i spent 5 hours looking into this. I NEED HELP!
Click to expand...
Click to collapse
..... It says that on every One X, it's HTC telling whoever turns the phone on that you used HTCDev.com
Make Sure you have TWRP (recovery) flashed/installed ... then in the bootloader go into recovery and flash cm10 ... and since you probably have the newer hboot 1.14 that means that you HAVE to flash the kernel (boot.img) via fastboot
Which is simple,
flash cm10
then reboot into the bootloader > fastboot
extract the boot.img from the cm10.zip
and fastboot flash boot boot.img
then your done reboot and enjoy.... (anything else read threw the forum, all your answers have been asked by somebody else already)
On rogers he won't have the 1.14 hboot, which means all he has to do is install the rom.
Try flashing the recovery again (TWRP ONLY!)
And then reinstall CM10
Tachi91 said:
..... It says that on every One X, it's HTC telling whoever turns the phone on that you used HTCDev.com
Make Sure you have TWRP (recovery) flashed/installed ... then in the bootloader go into recovery and flash cm10 ... and since you probably have the newer hboot 1.14 that means that you HAVE to flash the kernel (boot.img) via fastboot
Which is simple,
flash cm10
then reboot into the bootloader > fastboot
extract the boot.img from the cm10.zip
and fastboot flash boot boot.img
then your done reboot and enjoy.... (anything else read threw the forum, all your answers have been asked by somebody else already)
Click to expand...
Click to collapse
Can you post download to to what you're refering to ? I want to delete all my old files and redownload it all, starting fresh.
ugh crap im so lost , i don't get what to install like .. i flash CWM and it doesnt work and all that omg . Can we skype or somethng so we can do this step by step ? :$
Lasts3cond said:
i flash CWM and it doesnt work and all that omg
Click to expand...
Click to collapse
That might be your problem. CWM isn't supported for this phone and has been known to corrupt data.
Links for all the files you need are in a sticky in the Development forum. Here's the link for TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
Once you've got that, you can wipe your phone inside TWRP (don't do it in bootloader--you'll have to reformat your sd card), and reflash CM10.
That link requires me to use that GOO manager? Confused lol i have TWRP on my computer but not sure the steps to use it ..
Lasts3cond said:
That link requires me to use that GOO manager? Confused lol i have TWRP on my computer but not sure the steps to use it ..
Click to expand...
Click to collapse
You can't use Goomanager if the phone doesn't boot. You need to push it over to your phone using adb, then you can flash it from recovery.
redpoint73 said:
You can't use Goomanager if the phone doesn't boot. You need to push it over to your phone using adb, then you can flash it from recovery.
Click to expand...
Click to collapse
Lol yeah i understand that and adb? I can't even past the screen where it shows fastboot , factory rest , shut down .. etc
Lasts3cond said:
Lol yeah i understand that and adb? I can't even past the screen where it shows fastboot , factory rest , shut down .. etc
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1754018
iElvis said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Beat me to it.
Read up, get adb working. Then you can install TWRP using adb.
So first i need to get adb working , then install TWRP to wipe my phone? To access that i flash TWRP and go into recovery right ?
EDIT: So .. i've downloaded that adb , and i got a bunch of files.. what do i do with this? I put them into my fastboot folder in my C drive.. Also i need to unlock my phone to do this right ? Cause i accidently relocked it .
EDIT: OKAY i rooted my phone , and got into TWRP , tried a factory rest under the wipe menu. http://i48.tinypic.com/13yklep.jpg It says fails.. what do i do ?
Go to mount usb storage (not sure which screen its on) while it's plugged into your computer
If windows says the card is corrupted, format it fat32, then copy over a rom onto your sd card
area51avenger said:
Go to mount usb storage (not sure which screen its on) while it's plugged into your computer
If windows says the card is corrupted, format it fat32, then copy over a rom onto your sd card
Click to expand...
Click to collapse
Okay got into mount http://i47.tinypic.com/2cq085x.jpg then a screen pops up , is this the one? http://i45.tinypic.com/m7ur08.jpg
EDIT: Okay so i need to copy a rom onto my phone via usb. Do i copy over the boot.img,system and NETA-INF from cm10 ?
So i put the cm10 zip onto my sdcard (my phone) and i got this when i want to install .. should i proceed? http://i45.tinypic.com/28uts7n.jpg
WAIT NOOOOO
That is an international rom
Get CM10 from THIS FORUM ONLY
http://forum.xda-developers.com/showthread.php?t=1790032
area51avenger said:
WAIT NOOOOO
That is an international rom
Get CM10 from THIS FORUM ONLY
http://forum.xda-developers.com/showthread.php?t=1790032
Click to expand...
Click to collapse
LOL okay ! But on that thread isnt that cm10 for AT&T HTC XL? :S I have a Htc one x rogers .
Lasts3cond said:
LOL okay ! But on that thread isnt that cm10 for AT&T HTC XL? :S I have a Htc one x rogers .
Click to expand...
Click to collapse
The Rogers HTC One X IS a HTC One XL. Rogers just branded it. The OneX has the Tegra 3 Quad Core Processor, the One XL has the S4 Dual Core Processor. Your phone is the same as the ATT Version. Trust me
Okay got the evita one but it still says same msg , should i proceed? :S
lasts3cond said:
okay got the evita one but it still says same msg , should i proceed? :s
Click to expand...
Click to collapse
omfg it works ty so much!
No problem. Just be glad you didn't flash an international Rom. They can render your device completely unusable. Remember only flash things from this forum and enjoy
Sent from my HTC One XL using xda app-developers app
area51avenger said:
No problem. Just be glad you didn't flash an international Rom.
Click to expand...
Click to collapse
After all that, lol. At least he had the sense to stop and ask.
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?
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.