SO guys pls help me im dying of my phone .
what i did was unlocked bootloader flashed cwm v 6.0.3.1 then wiped factory data and tried flashing artax cm11 4.4 rom .
now its bootlopping into cwm .
pls help im litreally crying
@kuma82 @cmahendra and all pls
Not sure if cwm 6.0.3.1 is the correct recovery for CM11. I think you need 6.0.4.* not sure. If installing cm11 isn't the problem, the issue might be that the cwm (for cm11) isn't wiping the data (factory data).
You should install a previous version cwm and wipe the data with it.
You should ask @artas182x he compiled the cm11 and cwm.
kuma82 said:
Not sure if cwm 6.0.3.1 is the correct recovery for CM11. I think you need 6.0.4.* not sure. If installing cm11 isn't the problem, the issue might be that the cwm (for cm11) isn't wiping the data (factory data).
You should install a previous version cwm and wipe the data with it.
You should ask @artas182x he compiled the cm11 and cwm.
Click to expand...
Click to collapse
thanks kuma bro for replying. here in this forum of this phone, it's a big achievement if someone replies.
now to the situation,
further then, working with jishu sir, I did a lot of things and finally ended up in situation where
1. sw mode worked but showed BL unlocked.
2Normal reboot, any kind of booting lead to white screen with rainbow lines.
then tried offline fix guide, it was getting stick at 15% .tried for 6 hours with a lot of tension.
today went to svc with fear as they might now (by bl unlocked msg while in sw mode) and decline warranty and I end up with 340$ gone kaput.
they took 30min and gave working factory like phone back.
now no Bl, root, Rom for me until I get a phone like nexus 5 or note with universal one type 5 min methods to do all thing at once with 99.9% accuracy.
thanks you, artax, cmahendra sir.
adios xda. .
devilanuj17 said:
thanks kuma bro for replying. here in this forum of this phone, it's a big achievement if someone replies.
now to the situation,
further then, working with jishu sir, I did a lot of things and finally ended up in situation where
1. sw mode worked but showed BL unlocked.
2Normal reboot, any kind of booting lead to white screen with rainbow lines.
then tried offline fix guide, it was getting stick at 15% .tried for 6 hours with a lot of tension.
today went to svc with fear as they might now (by bl unlocked msg while in sw mode) and decline warranty and I end up with 340$ gone kaput.
they took 30min and gave working factory like phone back.
now no Bl, root, Rom for me until I get a phone like nexus 5 or note with universal one type 5 min methods to do all thing at once with 99.9% accuracy.
thanks you, artax, cmahendra sir.
adios xda. .
Click to expand...
Click to collapse
you can use lgflashtool to back too stock
but o thing it back to locked bootloader
http://forum.xda-developers.com/showthread.php?t=2686746
Related
I must humbly ask for everyone's help. I bought a Galaxy S3 (Sprint) today and rooted no problem. I downloaded font changer and Rom Toolkit. I changed a font and clicked "reboot" and the phone hung on the reboot screen--after the sprint logo and says "Samsung" with the blue light going up and down in intensity.
I tried a cache clear and data wipe, neither of those worked. I also tied reflashing the root ROM. That didn't work.
My most recent steps were to flash the stock recovery and stock ROM. It still hangs. I can get to recovery and am able to flash with ODIN. What should I do next?!
If nothing else, is there a way to reset the flash counter so I can maybe get Sprint to fix it? The only way I saw is to download an app, which won't work.
Any help is appreciated, I've tried all that I could think of.
UPDATE: Maybe there is no ROM installed anymore? I'm downloading the full Omega ROM. Anyone have a link to the sprint stock rom?
brickeds3 said:
I must humbly ask for everyone's help. I bought a Galaxy S3 (Sprint) today and rooted no problem. I downloaded font changer and Rom Toolkit. I changed a font and clicked "reboot" and the phone hung on the reboot screen--after the sprint logo and says "Samsung" with the blue light going up and down in intensity.
I tried a cache clear and data wipe, neither of those worked. I also tied reflashing the root ROM. That didn't work.
My most recent steps were to flash the stock recovery and stock ROM. It still hangs. I can get to recovery and am able to flash with ODIN. What should I do next?!
If nothing else, is there a way to reset the flash counter so I can maybe get Sprint to fix it? The only way I saw is to download an app, which won't work.
Any help is appreciated, I've tried all that I could think of.
UPDATE: Maybe there is no ROM installed anymore? I'm downloading the full Omega ROM. Anyone have a link to the sprint stock rom?
Click to expand...
Click to collapse
My only suggestion is to do a full wipe again (not just cache mind you) and then install the latest ROM for a Sprint phone one more time. Did you not do a nandroid backup that you could restore? Always do a nandroid backup before messing with any part of the phone for this very reason. I'm not harping. I'm just saying in the future it will save you from this issue.
P.S. This is the International thread. You better not be flashing your Sprint S3 with an International S3's ROM. That's a big no-no...
UPDATE:
*sigh*
Sprint Samsung Galaxy S3 Android Development Thread
Omega doesn't have a ROM for the Sprint version. You need to pay more attention before flashing your ROM's. Get a ROM from the above link, and never do anything without doing a nandroid backup first. Seriously.
I think I'm screwed
I reinstalled the Sprint software twice before I tried the other rom. Nothing worked. The Omega rom has me completely bricked.
I ordered a jig to see if that helps and will take it to a cell phone store in town (not factory) to see if they can get it into download mode. I have the sprint .tar bootloader thanks to this forum.
This was my first root and I never heard of the nandroid backup. I hope I can fix this for a $100 bucks and it isn't a $1000 mistake.
brickeds3 said:
I reinstalled the Sprint software twice before I tried the other rom. Nothing worked. The Omega rom has me completely bricked.
I ordered a jig to see if that helps and will take it to a cell phone store in town (not factory) to see if they can get it into download mode. I have the sprint .tar bootloader thanks to this forum.
This was my first root and I never heard of the nandroid backup. I hope I can fix this for a $100 bucks and it isn't a $1000 mistake.
Click to expand...
Click to collapse
1. Do you currently have the stock recovery or a custom recovery (e.g. CWM)? If you have stock recovery go to question 2, otherwise go to question 4.
2. Are you able to flash custom recovery via appropriate steps? If yes go to question 3, otherwise I think you're screwed.
3. Flash custom recovery.
4. In custom recovery do a full wipe.
5. Download THIS ROM to your SD Card and then flash in recovery.
6. See if the issue is resolved. If the issue is resolved that's fantastic. If the issue is not resolved then I'm pretty sure you're screwed.
Thanks
Thanks for that! Tomorrow I'm taking it to a custom cell phone repair/unlock store to see if they have a jig. If they do I'll try these steps, if not we'll see if my carrier is understanding...
I think moderator in development section should make compulsory to any developers make very big warning to anyone who read development thread. Many case carrier based phone come here to ask and flash ROM.
Sent from my GT-I9300 using Tapatalk 2
apisfires said:
I think moderator in development section should make compulsory to any developers make very big warning to anyone who read development thread. Many case carrier based phone come here to ask and flash ROM.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
The developers can't make it any more clear. The user is already clicking on Samsung Galaxy S III I9300. That isn't the phone they have. The developers can't be held responsible for users that refuse to read.
ive done the same exact thing and need to figure out how to fix it!!! did you find a cure for it yet?
brickeds3 said:
I reinstalled the Sprint software twice before I tried the other rom. Nothing worked. The Omega rom has me completely bricked.
I ordered a jig to see if that helps and will take it to a cell phone store in town (not factory) to see if they can get it into download mode. I have the sprint .tar bootloader thanks to this forum.
This was my first root and I never heard of the nandroid backup. I hope I can fix this for a $100 bucks and it isn't a $1000 mistake.
Click to expand...
Click to collapse
Remove your battery ..wait for 5 min...insert it and try to go into download mode. if you can get the correct rom and flash it.
Hello. About a month ago I rooted my phone using this guide http://forum.xda-developers.com/showthread.php?t=2189646. Everything went great until today. Few hours ago I received a system update (about 10MB) and installed it. And since then every time I reboot my phone I get ClockworkMod recovery menu showing up on my screen. I tried pulling out the batery, I even made a factory reset, but it still gives the the CMW menu every time I reboot my device. Maybe anyone of you could tell me what to do? Cause I'm kinda panicking right now
P.S. I also made such thing as "format /system" through "mounts and storage" menu. I don't know why, but I think it should be mentioned (just in case)
Well the best way now will be to download CWM backup for your phone from this thread, send it to sdcard and just recover using CWM. This way you won't lose root and CWM. If it won't work just you use KDZ to flash ROM from scratch. Check this thread too: http://forum.xda-developers.com/showpost.php?p=36352031&postcount=3
anirion said:
Well the best way now will be to download CWM backup for your phone from this thread, send it to sdcard and just recover using CWM. This way you won't lose root and CWM. If it won't work just you use KDZ to flash ROM from scratch. Check this thread too: http://forum.xda-developers.com/showpost.php?p=36352031&postcount=3
Click to expand...
Click to collapse
Thanks you. One more question. How do i know which CWM recovery to download? There are two Jelly Bean ones
Feero21 said:
Hello. About a month ago I rooted my phone using this guide http://forum.xda-developers.com/showthread.php?t=2189646. Everything went great until today. Few hours ago I received a system update (about 10MB) and installed it. And since then every time I reboot my phone I get ClockworkMod recovery menu showing up on my screen. I tried pulling out the batery, I even made a factory reset, but it still gives the the CMW menu every time I reboot my device. Maybe anyone of you could tell me what to do? Cause I'm kinda panicking right now
P.S. I also made such thing as "format /system" through "mounts and storage" menu. I don't know why, but I think it should be mentioned (just in case)
Click to expand...
Click to collapse
Feero21 said:
Thanks you. One more question. How do i know which CWM recovery to download? There are two Jelly Bean ones
Click to expand...
Click to collapse
If you share which L9 variant you have, which country rom you flashes or stay, then people will be able to help/tell you, which cwm backup is suitable to your L9.
Update your profile with your country name (if u r not criminal? lolz kidding), operator name and add L9 variant in your signature. at the moment, your profile is completely naked.
Ok, I managed to deal with my problem. Firstly I tried using cmahendra's guide on installing KDZ offline, but after aproximately 2 hours of complete failage I began searching for other ways. Luckily user edriskus answered to the message I sent him and suggested me doing the same as I tried to do before. He didn't mention the offline version so I thought that I should try the "online" one. And it worked! I don't really know how it sounds in numbers, but now my phone says that it has 4.1.2 version of android (hopefully the latest one available for L9).
There are few questions left:
1. Does my phone remain rooted or I have to root it once again (since I have reinstalled the software)
2. This one confuses me the most. Now my phone feels very laggy (which is strange, because it was factory reset previously and there aren't any apps here). I feel it from sliding menu/photos, surfing the settings and other similar actions. Maybe there is a way to fix it?
Nevertheless, my phone is working again and I really appreciate your help, fellows!
hello
Hello! I have exactly the same problem! Can you please explain to me how you manage to deal with it? I tryed to flash after this method http://forum.xda-developers.com/showthread.php?t=2085344 but i stuck at step 6 at the Post-JB issue, since every time I reboot my phone I get ClockworkMod recovery menu. Its a dead end for me. Pls help and thank you very much!
I finally succeded! Thx Feero21 for helping me, i followed your advice by trying it in "online" method. But there is one more problem, after i flashed the Rom i saw that i have only 1 gb free on my internal storege and another one occupyed. In total i have 2 gb instead of 4. I belive that the old Rom wasnt deleted and its still their and its occupying my also too small space. what can i do? Thanks!
Here's the story in short,
I bought a new LGOG a week ago.
Rooted it.
Running on stock 4.1.2 Jellybean , AT&T(unlocked for use with any operator).
Now , today I installed freegee and updated it. Took a backup of my EFS , and copied it in my external MMC.
Apart from that also attached the freegee with my dropbox account.
Now , I tried to install CWM recovery , but it seems that there was some sort of problem with download of CWM , as it was taking eternity. I waited for few minutes but then I rebooted the phone.
The phone actually didn't booted up fine. It's now stuck at LG logo , followed by a Google logo afterwards at the beginning with padlock symbol.
The logo stays there for a second and then the phone shuts down.
I panicked when I saw this , realizing that this may be a hard brick. Now I tried combination of volume keys , and it seems that it brought up a menu on the screen , with couple of options and information.
The options available are :
Start-
PowerOff-
Recovery Mode-
Restart boot loader-
The info available below are :
Fastboot mode
product_name : mako
variant -mako 16gb
hw version : rev_10 (88)
bootloader version : makoz10f
baseband version : n/a
carrier info : none.
serial number : 05959*******98de7**
signing- production
secure boot- enabled
lock state - unlocked
When I select reboot recovery , it reboots and then same as stated above. Seems as if the recovery is either not installed properly or is not working.
I was wondering that whether this is a complete brick or is there any chances of this being fixed ??
PS There's no warranty , it's an imported set from USA . SO cant avail it here .
A help would be really appreciated , willing to donate few bucks , if things work.
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
You can also read this thread, I just helped another person: http://forum.xda-developers.com/showthread.php?t=2556006
Let me know if you have questions.
aedren said:
You can also read this thread, I just helped another person: http://forum.xda-developers.com/showthread.php?t=2556006
Let me know if you have questions.
Click to expand...
Click to collapse
Thanks for your immediate reply Guys. That sounds really helpful.
It seems zombiegeek was able to fix the phone , and seems mine phone is in similar state.
I am going to go through the LGPNST and will see if that works. Searching for the tutorial thread on it.
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
Click to expand...
Click to collapse
I am going to go through it. Thanks for sharing.
EDIT : Successfully booted into Download mode By holding both the volume keys ( when device was completely switched off) and then plugging it into the PC using data cable.
It went straight to download mode.
Started LGNPST. Made sure that it detected my device. Registered LS970.dll file use rgsvr32.
Selected the DLL and BIN , and it went to 67% progress after start .
Rebooted , and went into boot loop.
I tried the same procedure again , but this tie with ATLBin instead of original Bin.
It rebooted and went into TWRP mode.
Finally a sigh of relief , as It booted into recovery.
Followed the steps as mentioned in the thread above. It worked!!
--------------
Haven't installed any ROMS yet.
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
Click to expand...
Click to collapse
same thing happened to my phone. Use freeGee to unlock and download cwm
but cwm download failed and have the same google logo and options.
just do the lgnst to stock.
Now I root my phone again. and not sure what should I do next.
so should I use the E970 Original TeenyBin to unlock bootloader and install cwm?
thanks
laofan said:
same thing happened to my phone. Use freeGee to unlock and download cwm
but cwm download failed and have the same google logo and options.
just do the lgnst to stock.
Now I root my phone again. and not sure what should I do next.
so should I use the E970 Original TeenyBin to unlock bootloader and install cwm?
thanks
Click to expand...
Click to collapse
Try the original teenybin, I think it includes twrp recovery. Don't worry about cwm. After flashing the bin boot into recovery and flash a rom. Again read the teenybin thread carefully and make sure you understand first.
PS. Original bin didn't work for me I had to use the other one. So if the same happens don't freak out.
optimusv45 said:
Try the original teenybin, I think it includes twrp recovery. Don't worry about cwm. After flashing the bin boot into recovery and flash a rom. Again read the teenybin thread carefully and make sure you understand first.
PS. Original bin didn't work for me I had to use the other one. So if the same happens don't freak out.
Click to expand...
Click to collapse
Yeah , I also want to stay away from CWM as long as TWRP is there.
What I am confused about is that if we flash the original JB bins from AT&T , will it leave the bootloader unlocked with TWRP recovery ??
All I need is Stock JB , with unlocked bootloader and TWRP recovery.
You said that original bins , didn't worked . DId you mean you used the ALTBin or something else ?
Rishi. said:
Yeah , I also want to stay away from CWM as long as TWRP is there.
What I am confused about is that if we flash the original JB bins from AT&T , will it leave the bootloader unlocked with TWRP recovery ??
All I need is Stock JB , with unlocked bootloader and TWRP recovery.
You said that original bins , didn't worked . DId you mean you used the ALTBin or something else ?
Click to expand...
Click to collapse
Yes, your bootloader will be unlocked and you will have twrp. Teenybin will not give you a working rom, it updates your phone to the newest software and give you a recovery. I think there is a bin that will recovery your phone to stock jb, you will have to look for it on the teenybin thread. Btw stock jb battery life is quite bad and there are quite a few stable 4.3 roms to choose from. Yes, I used altbin but that's just my phone. Original bin may work for you.
@Rishi.
here is the bin I use to go back to stock using LGNPST
http://forum.xda-developers.com/showthread.php?t=2219953
optimusv45 said:
Yes, your bootloader will be unlocked and you will have twrp. Teenybin will not give you a working rom, it updates your phone to the newest software and give you a recovery. I think there is a bin that will recovery your phone to stock jb, you will have to look for it on the teenybin thread. Btw stock jb battery life is quite bad and there are quite a few stable 4.3 roms to choose from. Yes, I used altbin but that's just my phone. Original bin may work for you.
Click to expand...
Click to collapse
Actually original TeenyBin , didn't worked in my case either.I had to flash the ALternative bins to make the TWRP work.It went into bootloop with original teeny bin , alt one worked though.
Good that the recovery is working now.
As you mentioned that the battery on stock Jb is bad , so I am going to leave that. But Can you confirm any 4.3/4.1 stable rom that has no issues whatsoever. ??
Rishi. said:
Actually original TeenyBin , didn't worked in my case either.I had to flash the ALternative bins to make the TWRP work.It went into bootloop with original teeny bin , alt one worked though.
Good that the recovery is working now.
As you mentioned that the battery on stock Jb is bad , so I am going to leave that. But Can you confirm any 4.3/4.1 stable rom that has no issues whatsoever. ??
Click to expand...
Click to collapse
The issues I encounter is insignificant comparing to how much benefit I gain. I run houstonns PA 3.99 RC 2 Adreno build . battery a lot better, less heat, deep sleep great, always wake up, fast and smooth, theme enabled too. Link for it http://forum.xda-developers.com/showthread.php?t=2228880 cm10.2 stable is also out. Bear in mind no one is gonna promise you you won't run into some issues and the stock rom isn't trouble-free either. If you are worried then you can just stick with stock for now. I honestly do like the stock rom, I think it looks great. Maybe eventually your curiosity will drive you to try custom roms.
PS: you can get stock running, make a backup, and then try some roms. Also now you know you have teenybins on your side, you should feel quite safe trying roms. Go with big name first , houstonns work is very good.
optimusv45 said:
The issues I encounter is insignificant comparing to how much benefit I gain. I run houstonns PA 3.99 RC 2 Adreno build . battery a lot better, less heat, deep sleep great, always wake up, fast and smooth, theme enabled too. Link for it http://forum.xda-developers.com/showthread.php?t=2228880 cm10.2 stable is also out. Bear in mind no one is gonna promise you you won't run into some issues and the stock rom isn't trouble-free either. If you are worried then you can just stick with stock for now. I honestly do like the stock rom, I think it looks great. Maybe eventually your curiosity will drive you to try custom roms.
PS: you can get stock running, make a backup, and then try some roms. Also now you know you have teenybins on your side, you should feel quite safe trying roms. Go with big name first , houstonns work is very good.
Click to expand...
Click to collapse
I have had experiences with lots of custom roms , MROm , Beanstalk , MIUI , CM7 , CM10 , etc, when I was an Atrix 4g user. The Roms have excellent performance difference . MIUI was best though as it had the appeal in terms of layout.
Anyways , unless I don't try one on LGOG , I am sure I won't be able to tell the difference.
BTW , I am going to try the Official Cyanogen 10.2 first.
If you flash the 11c or 20j bin you will be back to locked bootloader and no recovery. That is why I linked to flashable zip for 20j, it should work with twrp. Sorry for not being able to reply sooner.
Rishi. said:
I have had experiences with lots of custom roms , MROm , Beanstalk , MIUI , CM7 , CM10 , etc, when I was an Atrix 4g user. The Roms have excellent performance difference . MIUI was best though as it had the appeal in terms of layout.
Anyways , unless I don't try one on LGOG , I am sure I won't be able to tell the difference.
BTW , I am going to try the Official Cyanogen 10.2 first.
Click to expand...
Click to collapse
People are reporting issue with turning off NFC. They recommend either rebooting right away after booting into the rom or flash the rom again, So keep these in mind.
optimusv45 said:
People are reporting issue with turning off NFC. They recommend either rebooting right away after booting into the rom or flash the rom again, So keep these in mind.
Click to expand...
Click to collapse
installed cm10.2 , working good . seems stable with no issues , at least none with nfc yet.
will take a backup of this and will flash the stock bin with twrp.
adfurgerson said:
If you flash the 11c or 20j bin you will be back to locked bootloader and no recovery. That is why I linked to flashable zip for 20j, it should work with twrp. Sorry for not being able to reply sooner.
Click to expand...
Click to collapse
Thanks. It seems the Flashable zip you posted is better to use , since I went through the Flashable bins(.tot) thread and realized that rooting it back after LGNPSTing was kinda of doubtful.
Have taken CM10.2 backup. Will flash the TWRP/CWM flashable stock.
hi I am having trouble registering my dll files is there anyone that can help me?
nicklefloss said:
hi I am having trouble registering my dll files is there anyone that can help me?
Click to expand...
Click to collapse
Registering ?
The other day i was installing CrombiKK from Hairybean.
I followed the directions for the bootloader and recovery and installed it fine after many tries choosing different kernels and install methods in aroma.
I noticed after installing with some different kernels that the wifi bug had a separate fix and wasn't because of a faulty kernel so i went to reinstall with the wifi fix and the OC kernel i wanted and the rom installed just fine but i immediately installed the wifi fix and twrp gave me an error. the rom bootlooped.
i thought all was fine and wiped again to install again but i noticed that while installing the rom in aroma it took about 4 seconds versus a minute or so, and thats when i noticed that twrp wasn't writing any rom at all to the tablet.
so im stuck with no rom and twrp doesnt want to install the rom anymore when it worked previously. i have no backups on the tablet either.
i checked the brick guide -http://forum.xda-developers.com/showthread.php?t=1514088- and it seems to line up with brick #3 but they dont have any information on that.
please allmighty devs, help me.
-Forever-stallone
Seriously people should stop trying that rom ... it does more bad than good ... Last week the same happened to me ...
I am no DEV ! I was thinking I permanently bricked my tf201 so I was desperate and tried everything ... maybe think twice before attempting this ...
What version of twrp are you on ?? I believe that the first two steps you take to install CROMBi-kk (.recovery and .blob) basically turns your tf201 to tf300t . The evidence is when I installed cwm for tf201 it didn't work but cwm for tf300t worked pretty well . but generally cwm is useless in this case ...
I suggest make sure you are on latest twrp for tf300t device and go download latest official cyanogenMOD 11 for tf300t device and flash it with twrp.
Again, My case was way more messed up so I messed with many other stuff so maybe wait so someone confirm or deny this !? but I started going for CROMBi-kk now I got a fully working cm11 that thinks my device is tf300t .
S3P3HR said:
Seriously people should stop trying that rom ... it does more bad than good ... Last week the same happened to me ...
I am no DEV ! I was thinking I permanently bricked my tf201 so I was desperate and tried everything ... maybe think twice before attempting this ...
What version of twrp are you on ?? I believe that the first two steps you take to install CROMBi-kk (.recovery and .blob) basically turns your tf201 to tf300t . The evidence is when I installed cwm for tf201 it didn't work but cwm for tf300t worked pretty well . but generally cwm is useless in this case ...
I suggest make sure you are on latest twrp for tf300t device and go download latest official cyanogenMOD 11 for tf300t device and flash it with twrp.
Again, My case was way more messed up so I messed with many other stuff so maybe wait so someone confirm or deny this !? but I started going for CROMBi-kk now I got a fully working cm11 that thinks my device is tf300t .
Click to expand...
Click to collapse
You are completely correct to point out the dangers but the fact is if you follow the the instructions given in the respective threads to the letter then everything will be fine.
Unfortunately, years ago, Asus in their wisdom landed us with firmware that is totally unforgiving when mistakes are made. People do not understand this because they have spent many years flashing happily away on devices with zero penalties for making errors and have come to this forum expecting to just plough on as before. New people just don't seem to understand that a really small mistake can totally brick this device.
To be fair, the forum itself has for a long time now been hard to follow because outdated threads still keep rising to the top,
As one who has been knocking around here for a few years (and who will probably be stuck on the TF201 for a while yet now the new Nexus tablet keeps getting pushed back: 4:3 screen - wtf use is that for my portable TV/media device??) I will take some advice to put together an up-to-date warning post about what should and should not be tried. Experienced users please send PMs with suggestions on what should be included :good: .
S3P3HR-
I followed the instructions for crombikk exactly, hairybean 2.31 with JB 4.2.1, bootloader version 10.6.1.27.1 and twrp 2.6.3.1 and like i said i had it working at first minus the wifi patch that was a separate file.
the real problem was that i wanted to reinstall with a different kernel so i just booted into twrp and installed with aroma and it installed fine but twrp had an error when i immediately after installed the wifi patch. i didnt think much of it at first but now i cant install any roms.
Restorer-
You are deinitely right on this tablet being unforgiving. Ive been running custom roms since 2011 and have never had a problem like this before. It totally caught me off gaurd. i honestly didnt think this would be so bad, even my dad's evo 4g lte wasnt this easy to brick. Im mad about it though because that kitkat rom was the only thing to make it fast enough that i could use it how i like to use my devices.
Could you think about any possible way of fixing my rom installation problem? Its not like i can use it in its current state anyways so if theres a chance i would try it.
Forever-stallone said:
S3P3HR-
I followed the instructions for crombikk exactly, hairybean 2.31 with JB 4.2.1, bootloader version 10.6.1.27.1 and twrp 2.6.3.1 and like i said i had it working at first minus the wifi patch that was a separate file.
the real problem was that i wanted to reinstall with a different kernel so i just booted into twrp and installed with aroma and it installed fine but twrp had an error when i immediately after installed the wifi patch. i didnt think much of it at first but now i cant install any roms.
Restorer-
You are deinitely right on this tablet being unforgiving. Ive been running custom roms since 2011 and have never had a problem like this before. It totally caught me off gaurd. i honestly didnt think this would be so bad, even my dad's evo 4g lte wasnt this easy to brick. Im mad about it though because that kitkat rom was the only thing to make it fast enough that i could use it how i like to use my devices.
Could you think about any possible way of fixing my rom installation problem? Its not like i can use it in its current state anyways so if theres a chance i would try it.
Click to expand...
Click to collapse
Can you still access the bootloader when you hold down volume down and power button before going into recovery ?
flumpster said:
Can you still access the bootloader when you hold down volume down and power button before going into recovery ?
Click to expand...
Click to collapse
Yes, can access the boot loader just fine. I haven't checked if fastboot still works but it should since the boot loader does. I just am wary of trying anything with the risk of making it much much worse.
it has been 10+ days and since nothing helpful has been posted I post this .
I never installed the actuall rom but I installed recovey and .blob and it somehow formatted my /data with all my backups in it . then I panicked and tried to format partition Data and it took a little long so I panicked some more and forced a restart ... I found microSD card and tried to install cm10 and virtuous_prime roms but It was a fail . I investigated and saw my /data was corrupt and showed internal : 0mb . I was still able to flash any recovery I wanted . Usually cwm for tf300 and twrp ...
compare your case to mine and the case I post Down below ... it does Exactly what that on unbrick guide said not to do ... Your choice ... if every thing fails then a mainboard replacement is last option ...
Look at post #5 for his version of fix . I couldn't access asus tf201 official support site so I yahoo'ed stock firmware and for what its worth , I chose a rom that had deoxed in the name ... whatever that means ...
http://forum.xda-developers.com/showthread.php?t=2800506
S3P3HR said:
it has been 10+ days and since nothing helpful has been posted I post this .
I never installed the actuall rom but I installed recovey and .blob and it somehow formatted my /data with all my backups in it . then I panicked and tried to format partition Data and it took a little long so I panicked some more and forced a restart ... I found microSD card and tried to install cm10 and virtuous_prime roms but It was a fail . I investigated and saw my /data was corrupt and showed internal : 0mb . I was still able to flash any recovery I wanted . Usually cwm for tf300 and twrp ...
compare your case to mine and the case I post Down below ... it does Exactly what that on unbrick guide said not to do ... Your choice ... if every thing fails then a mainboard replacement is last option ...
Look at post #5 for his version of fix . I couldn't access asus tf201 official support site so I yahoo'ed stock firmware and for what its worth , I chose a rom that had deoxed in the name ... whatever that means ...
http://forum.xda-developers.com/showthread.php?t=2800506
Click to expand...
Click to collapse
Sorry for the late reply everybody, im up and running again after lj50036 (dev behind crombi) helped me so much. What we did was since the bootloader was working just fine we set the tablet back up with a stock blob and from there we set up NVFLASH (which was needed 10 mins later, haha) and after that i used it to take my tab back to stock and from there i followed his instructions for crombi.
BTW, crombi is literally the fastest rom i have ever used on the tf201, the battery life is lowered a bit because of OC but its worth it.
@ s3ph3r, you might have gotten yourself into a big mess, does your bootloader still work? if so, there may be hope but i couldnt figure out where to start with it.
First hello people who'll come here.
So here is the issue. I tried to root my Honor 7 and everythings did well to the moment when i want to leave recovery mode by a reboot. At this moment i was blocked in TWRP. I searched how to leave it and i found this http://forum.xda-developers.com/showthread.php?t=1845768 but i don't know if it works cause when i managed to leave recovery mode and go in bootloader i totally forget this. I was in bootloader and my first reaction was to change the version of TWRP beacause mine was in chinese so a little bit more complicated. But whith this process i put the phone in a bootloop. So i asked to you if someone could help me first to leave this bootloop without wait for the battery (all passed yesterday but actually the phone do not have enought battery so i managed to go in bootloader mode) and help to leave TWRP if i do again the manipulation.
Thanks in advance.
I followed this http://forum.xda-developers.com/honor-7/general/how-to-root-honor-7-t3170735
P.S: Sorry if there are mistakes, if my post isn't in the good category and if a post like this already exist because i searched and i didn't find anything to help me.
If it can interest someone i have now a black screen after tried to flash again twrp and reboot
Please someone ?
Pepito11 said:
First hello people who'll come here.
So here is the issue. I tried to root my Honor 7 and everythings did well to the moment when i want to leave recovery mode by a reboot. At this moment i was blocked in TWRP. I searched how to leave it and i found this http://forum.xda-developers.com/showthread.php?t=1845768 but i don't know if it works cause when i managed to leave recovery mode and go in bootloader i totally forget this. I was in bootloader and my first reaction was to change the version of TWRP beacause mine was in chinese so a little bit more complicated. But whith this process i put the phone in a bootloop. So i asked to you if someone could help me first to leave this bootloop without wait for the battery (all passed yesterday but actually the phone do not have enought battery so i managed to go in bootloader mode) and help to leave TWRP if i do again the manipulation.
Thanks in advance.
I followed this http://forum.xda-developers.com/honor-7/general/how-to-root-honor-7-t3170735
P.S: Sorry if there are mistakes, if my post isn't in the good category and if a post like this already exist because i searched and i didn't find anything to help me.
Click to expand...
Click to collapse
so,to leave the bootloop,you need a stock ROM/custom ROM for your device and flash it,it should recovered from bootloop,
and if you try to root it again,i suggest you to use another guide of how to root it and by following your phone model..
Instructions:
1.Download the Stock ROM/Custom ROM for your phone model,make sure the rom is the same model for your device or else,you're gonna be in a bootloop again,all phone model are practically not the same! remember this if you attempting to modified your device
2.after the rom has been downloaded,put the rom in any sd card,and then insert sd card that have the rom in it.
3.in this case,you need to format the system,data,cache, formatting the data is optional though,but if it still bootlooping,consider yourself to format the data,if you want the data to not be erase,dont format it or if you want a clean install,backup the Data
3.Flash the rom using the TWRP recovery that you have installed
4.Reboot to the system
And the problem are gonna fixed