[Q] [HELP] TWRP does not read SD - AT&T LG Optimus G

After many lost hours of sleep, I finally give up and come to the community for help. I've seen the problems I'm having posted a lot, but I've not yet found a solution.
To start, all was well with my KitKat 4.4 ROM, except that my SIM would not read. So in my troubleshooting process, I did a full system wipe of everything through TWRP v2.6.3.0 (including internal memory), knowing that my ROM and other necessary files were saved on my SD card. The problem now is that TWRP will not show that I actually have an SD, so I'm stuck with no OS now. I've tried everything I've seen, such as formatting and properly "ejecting" the SD from my computer after doing so. I've tried three different SD cards, two 16gig and one 2 gig. Still won't read.
The only other thing I can think to do is use ADB to push or sideload - my device does not show at all when I try. Same result with fastboot. I'm suspecting that the issue with this is the driver. So far, after searching for hours and hours, the only driver I've found to use with the E970 is the usb_driver downloaded through SDK Manager. When I use this driver, it shows my phone as Google Galaxy Nexus ADB Interface in the Device Manager. But still no luck with ADB or Fastboot.
So I apologize if either of these has been solved one or more times before, but I'm desperate for help. Thanks!

AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.

Rishi. said:
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Click to expand...
Click to collapse
As of right now, my phone has no ROM installed. I'd be willing to bet that it wouldn't read from an SD even before I tried my first ROM, but I don't really know since I never tried. Stupid on my part for not doing so before the wipe. I'll look into the modded TWRP, and hopefully it'll get me somewhere. Thanks for the help!

I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.

Rishi. said:
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Click to expand...
Click to collapse
The problem with this is that I can't get ADB to find my device. If that were the case, I'd just push the ROM straight to my internal memory since that's the only one it sees. I've tried and double checked many times to make sure I was doing the ADB process properly. As far as I can tell, I am. Which leads me to think its not the proper driver for my phone. But I can't find any others.
I thought about LGNPST, but I can't get the phone into download mode without an OS. And that's the only way I know to use LGNPST.

You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.

Rishi. said:
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Click to expand...
Click to collapse
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!

SmithZ33 said:
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
Click to expand...
Click to collapse
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:

Rishi. said:
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Click to expand...
Click to collapse
Well, I opted to use LGNPST to flash TeenyBins and a TWRP that read my SD. Flashed the KitKat ROM just to try it, and it boots perfectly but I'm back to no SIM. So I'll be moving on to this new issue... haha

So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk

Rishi. said:
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
Haha, no I didn't. Between work and travel, I'm still trying to figure out this sim issue. It won't detect my sim on this ROM, or others it seems. I tried on a LiquidSmooth 4.3.1 ROM just now and it had the same issue. It's almost as if it has the detection set backwards. When I insert the sim, it thinks I've removed it and says ”sim removed." Then when removed, it says ”sim inserted” or something along those lines, and wants to restart. I'm at a loss, and I'm wondering why it could be doing this.

Related

NRGROM boot loop

Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
ten6 said:
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
Click to expand...
Click to collapse
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Dark Nightmare said:
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Click to expand...
Click to collapse
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
ten6 said:
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
Click to expand...
Click to collapse
Don't download that one, it has issues, hold up, I'll give you a link to the most recent file.
Here, get this: http://d-h.st/3VD
Download speed should be faster as well. rename it PH85IMG and place it on your sd card after you relock your bootloader, then boot into bootloader, it's gonna detect the file and ask you if you wanna update, follow the on screen instructions to update, voila! Follow the basics to install the new energy rom.
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It is useful, I fully agree with you, it's like we come here to answer the same questions over and over, but I'm just trying to be nice, cause I usually just say, read the amaze bible, but then they go and do something even more noobish, so to avoid the tear jerks I just give the basic info, though I'm fading away slowly.
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
I came across this issue. As earlier posts said, install the new ICS update. The partitions were messed up and the ruu will clean it up.
ten6 said:
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
Click to expand...
Click to collapse
Lol, never pointed fingers buddy, so calm down.
Maybe I should create a new topic but my issue is similar to this one except for the fact that I read quite a lot and tried quite a few things.
My situation is that I made a backup with cwm only booted not flashed so I have the 100% stock backed up, after this I flashed cwm and tried to install the Energy rom based on ics and that was my mistake as I used to be on a Nexus device I didn't have to worry about this.
So I got stuck on a bootloop and tried factory reset/wiping everything, tried to reinstall a stock ROM (t-mobile one as I only found a .exe for the videotron one and I did not feel like exploring the exe as I am a Linux user) by relocking bootloader and using the HTC method, tried to install manually the stock Kernel with Energy ROM using adb and fastboot commands, tried to restore my backup but nothing seems to work, I'm still bootlooping.
Is-it possible to s-off without a regular adb access (only the cwm adb access)? And would s-off allow me to flash anything as I wish? Is there a way to have any ROM working on my device? (i know the answer is yes to the last one, at least )
Thanks!
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
johnride said:
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
Click to expand...
Click to collapse
Okay okay, calm down, there's currently only one method of going about restoring your device since you're s-on and no you cannot s-off with just cwm adb, I think JB s-off method is only an exe file, never saw linux files anywhere on his site. Anyways, you have to use the GB exe for videotron and restore to stock via it then update to ics to use the most recent energy rom, BUT if you just want a working device, this is just an idea, though it should work fine, you can flash a custom recovery and flash the GB version of energy rom, you should be able to restore your backup as well, but you said you can't, which is odd, it may be because of the kernel not being flashable as since CWM cannot flash kernels while s-on, in which case I'd advise you to get 4EXT recovery and then try restoring your back once again, it should work fine since 4EXT can flash kernels while S-ON.
My two cents.
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
johnride said:
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
Click to expand...
Click to collapse
I got lost halfway through that post, after flashing a rom, if the kernel isn't flashed (reboots and does it automatically), then flash the kernel manually, should boot fine, does anyone ever really read anymore? This very issue both s-on and s-off has been answered more times today than I can count. If you read the details on JB's site, you'd see and know all you need to.
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
johnride said:
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
Click to expand...
Click to collapse
How did you go about flashing the kernel?
Sent from my SGH-T679 using xda app-developers app
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
johnride said:
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
Click to expand...
Click to collapse
Okay here's a few tips, cwm cannot flash kernels with son devices, get 4ext recovery for that. Second thing, reflash the from after doing a super wipe, if 4ext doesnt reboot and flash the kernel, do it manually, ill assume you know how to use ad, if not check my Bible tutorial on it, use the boot command for flashing boot images, take the boot file from the zip file, place it in the folder where your adb files are and flash it to your device while its in fastboot mode.
Sent from my SGH-T679 using xda app-developers app
Well, I think I have done all you mention above, the only thing i'm not sure to understand is what you mean by "super wipe" I found some executables about it but I guess it can't do much more than the flash all partitions (except external sdcard) in 4ext recovery wich I finally managed to install properly.
So, I made that global formatting thing, I tried to install an ICS based ROM and 4ext rebooted to install kernel, same bootloop. Tried to install manually the kernel that came with this rom via the classic fastboot flash boot boot.img. Same bootloop. Tried to put the modules manually via the recovery adb access (performing a mount -a in adb shell to have everything present in fstab mounted) and flashing this stock kernel with no more success.
Achieved the same operations with a GB based ROM (this one: http://forum.xda-developers.com/showthread.php?t=1535173) with both the faux and the stock kernel without any more success.
Did I miss something? Am I so dumb? Do you have any other rom to suggest that have higher chances to succeed?
Do you think trying to restore my sotck nandroid with 4ext has more chances to succeed?
Thanks, again and always!

Biggest regret trying to Root & Flash! (PLEASE HELP REVIVAL)

Sigh...
Sorry to rant here. hoping i can get answers, to common problems obviously but even though i researched & tried many stuff that i'm unfamiliar with, after 15hours trying, i decided to post.
Certain issues came up while flashing, some fixed(accidentally), but now my HTC one x+ (Asia), which was perfect, is stuck with a non-working ROM which does't get any Radio (no network/sim), also the SD card (internal) is not detected.
I JUST WISH TO GO BACK TO STOCK ROM NOW...
I know how to UNLOCK it using ALL IN ONE TOOLKIT.
I'm now dowloading (on a slow internet in Philippines) an (OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_0.23a.32.09.29_10.128.32.34a_release_299070u0mcx8aiaku8jgn4.zip),
hoping i will be able to go to Bootloader, fastboot & just click the RUU?
(honestly i dont even know if it will be an EXE, & the correct way)
I'm just hoping if i can re-lock the device, and run a RUU exe, i will have my phone again.
What i did to end up like this below (if anyone bothers to read)
first it was stuck at boot, then i flashed more stuff im aware of, trying to fix anything. i think i shall skip mentioning what i tried as i myself not sure what i did.
bottom line, now the htc one x+ turns on, charges, gets wifi (but no data network & no sd storage)
SD card (while detected, was wiped clean) - no ROMS there now.
I cannot go into RECOVERY BOOT, and pc sometimes recognises the ONE X+ device, but not as a storage card!!??
I have no backup in the Sd anyway..
someone please help me...
i think my post above doesnt make sense, as im so tired trying to fix it by researching.
if there is a simple STEP BY STEP guide to going back to stock ROM please help.
(i'm guessing what i can find for HTC one x can also be used for HTC one x+???)
i saved up many months for this phone.
i loved it so much, & it was perfect, but i wanted to try tweaking & trying the 4.2.1...
i regret it so much as im stuck..my brain is not working anymore after reading so much..
hi
to anyone who can give me a quick reply..
at this point, i have no ROM in my HTC One X+
I am trying my hardest to get back the stock ROM
so now im downloading the RUU exe.
RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.14.707.16_Radio_3.1204.167.31_release_290413_signed.exe
I really think thats the right one for my CID
NOW, after it completes download, (in about 3more hours!)
I intend to RE-LOCK my phone.
Go into FASTBOOT, connect to PC & simply RUN the RUU exe file..
MY QUESTION
Is this the right way? i tried with another RUU exe whih was for Cingular,USA, obviously it said WRONG RUU! but it was starting to TRY TO FLASH/INSTALL etc..so it seems like if i get the right RUU it will work??
(i found some links to use the COMMAND PROMPT but i tried & i still cannot get it fixed..)
please..i know this is all a common problem.. but i really just want my phone back.. at least to working condition..
im now thinking of bringing it to some repair shop, but i don't know anywhere here that can fix android or HTC.. i'm in Cebu, philippines by the way...
Sideload
You can try adb sideload option with TWRP recovery and a custom ROM. That should solve your problem. Finding correct RUU and installing them does not work easily most of the times.
To revert back to your original RUU, you need to
- relock your bootloader
- go to USB fastboot (connecting the the phone to your PC)
- run your Asian RUU from PC and follow instructions and wait
Thank you Steve0007 (I like your Avatar!)
Yes, i'm hoping it will be simple...
(Is it correct after i relock the device, the bootloader shows RE-LOCKED!?? , just curious as i don't know what it says before.. shouldn't it say.. LOCKED??).. oh well..
Sadly i'm using super slow internet to download whatever i can...
now i'm waiting for the Asian RUU (executable) to be downloaded, so i can try this method!
In the meantime..i'm gonna keep reading up about other methods.
thnks so much!
Steve0007 said:
To revert back to your original RUU, you need to
- relock your bootloader
- go to USB fastboot (connecting the the phone to your PC)
- run your Asian RUU from PC and follow instructions and wait
Click to expand...
Click to collapse
Abhishek.chaurasia said:
You can try adb sideload option with TWRP recovery and a custom ROM. That should solve your problem. Finding correct RUU and installing them does not work easily most of the times.
Click to expand...
Click to collapse
Hi Abhishek... thank you for all the Messages in inbox... relieved to get some help..at least..this phone is my baby..
I see, ... while waiting for the RUU to be downloaded, i think i shall try to find out how to do TWRP recovery!
I have One_X+_All-In-One_Kit_v2.3 (by Hasoon2000)
somehow it doesnt show TWRP...
it shows CWM (ATT),
and CWM International
and Your Own Recovery
i'm sorry i ask so many newbie questions.. but its really helpful for people who are in panic..
(on a sidenote, .. my wife thinks im crazy trying to (HACK-her words.. JAILBREAK-her understanding.. -SPOILING-her verdict) a perfectly fine phone!..)
I've been flashing ROMS and customising stuff on WINDOWS MOBILE since 2005/6 since the O2 Mini days.. but now i decided to 'ply' around with my device and find out i know NUTS!
I feel for you mate I did same after a week of trial and error I managed to adb sideload a Rom hope u get it fixed
Sent from my HTC One X+ using xda app-developers app
Abhishek.chaurasia said:
You can try adb sideload option with TWRP recovery and a custom ROM. That should solve your problem. Finding correct RUU and installing them does not work easily most of the times.
Click to expand...
Click to collapse
Oh..by Custom ROM, you mean one of those suitable ROMS found here right?
Which means i should ensure its UNLOCKED..
i now have in my hard drive...these ROMs downloaded..will these do??
OTA_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9-1.26.401.2_release_257085oc51j7moynlstgb9
Slim-4.2.1.stable.1.0-enrc2b-20130216-1511-UNOFFICIAL
flashing regrets... maybe just temporary
andy1969 said:
I feel for you mate I did same after a week of trial and error I managed to adb sideload a Rom hope u get it fixed
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Yes Andy1969, thanks.
I've been trying for about 17hours total now... (i realise i must be not as 'techie' as i thought!)
i have refrained from flashing ever since i got HTC touch, Touch Dual, Diamond, HD, Sensation, One X and now finally got my dream phone One X+.. which is almost perfect.. But i had an itch to start fiddling with it after owning it for just about 2 months...
even though i regret it, at this moment.. i feel that somehow after i learn more..my addiction to flashing may come back just like in those Windows Mobile days!
TWRP2
DELETED
TWRP
First try the RUU you have downloaded. If not, then unlock again and install TWRP from this link http://teamw.in/project/twrp2/130 and try sideloading Slim Rom you have downloaded.
Abhishek.chaurasia said:
First try the RUU you have downloaded. If not, then unlock again and install TWRP from this link http://teamw.in/project/twrp2/130 and try sideloading Slim Rom you have downloaded.
Click to expand...
Click to collapse
I managed to install TWRP!
now when i choose RECOVERY it goes straight to the TWRP...
i dont really know why the SLIM ROM sideloading did not work... as in SD card (as stated in TWRP) shows only the TWRP folder...
but at least im seeing progress...
i will keep trying sideloading some ROMS... maybe need to change name of file etc??
anyway..when i got into TWRP..1st thing i did was back up... at least for now..its better than being totally bricked...
i am back into the non-fully-working AOKP Jelly Bean 4.2.1 Custom ROM which doesnt recognise my sim or my sd card...
I DID IT! (i think..i hope)
WELL...
by some fluke.i managed to use TWRP to sideload the SlimBean ROM.. wow... 1st it was all error..so since its in the SD partition, i used TWRP recovery to reflash...still many buggy errors... network was found but no calls can be made.. now i did a factory reset from the phone settings itself.. (not the TWRP) and wala... all seems to be fine..
wifi, text, calls all ok..
yet to test others.. its 12.45am now!
so i spent 2 full days for my silly trial... but its ok.. i learnt stuff anyway..
BUT the SD card problem still exists... no detected..will work on it tomorrow or try new roms etc..
but the SlimBean interface & 4.2.1 is really cool & different..
im pretty sure there will be some errors tomorrow.. (just have a feeling)..if not.. then it will be best..
for now.. HOME button doesnt get me back to HOME! (will try settings etc)..now checking out other settings before i get some rest!
cheers.. will update again tomorrow..
Good progress. Now you know how to bring your phone back to life
c2nitz said:
WELL...
by some fluke.i managed to use TWRP to sideload the SlimBean ROM.. wow... 1st it was all error..so since its in the SD partition, i used TWRP recovery to reflash...still many buggy errors... network was found but no calls can be made.. now i did a factory reset from the phone settings itself.. (not the TWRP) and wala... all seems to be fine..
wifi, text, calls all ok..
yet to test others.. its 12.45am now!
so i spent 2 full days for my silly trial... but its ok.. i learnt stuff anyway..
BUT the SD card problem still exists... no detected..will work on it tomorrow or try new roms etc..
but the SlimBean interface & 4.2.1 is really cool & different..
im pretty sure there will be some errors tomorrow.. (just have a feeling)..if not.. then it will be best..
for now.. HOME button doesnt get me back to HOME! (will try settings etc)..now checking out other settings before i get some rest!
cheers.. will update again tomorrow..
Click to expand...
Click to collapse
You keep saying "SD Card" problem. What do you mean by that? You do understand our phone has no SD Card or SD Card partition. What you think of as the SD Card is nothing but a folder called "media" on the /data/ partition. That means we can't do things like mount our device as mass storage on PC's or mount SD Card in recovery.
Sent from my HTC One X+ using Tapatalk 2
Nvm
Sd storage
AndroHero said:
You keep saying "SD Card" problem. What do you mean by that? You do understand our phone has no SD Card or SD Card partition. What you think of as the SD Card is nothing but a folder called "media" on the /data/ partition. That means we can't do things like mount our device as mass storage on PC's or mount SD Card in recovery.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Yes i understand it doesn't have a 'physical' SD Card, but in Stock Rom, in File Explorer, it is recognised as SD Card.
Also, when plugged into PC, it is recognised as External Storage... from PC, it was possible to access the Internal Storage, and within that, the SD Card, which inluded DCIM, and whatever folders it had..
BUT now all tht 'SD' portion is gone.. Gallery cannot be viewed as there is no 'SD Card' (system prompt)
Camera doesn't work too as there is no 'SD Card' (system prompts again)
Help pls! Rom is gone! Usb unrecognized!
NOW its worse!! pls help!
I woke up this morning, turned the HOX+ on...
I found that most functions not working! (example-FILE MANAGER/CAMERA/BROWSER HAS STOPPED WORKING PROMPT,etc)
I knew that i will try re-flash today, so i went into TWRP recovery again & re-flashed the same SLIMbean rom.
still didnt work, so i wiped data etc...
I didnt realise I ALSO WIPED AWAY EVERYTHING!
SO NOW THERE IS NO ROM AGAIN..
if i boot it's STUCK AT HTC QUIETLY BRILLIANT screen, and worst, if i go into FASTBOOT, when i plug the usb into my Windows 8 PC, it DOESN'T say FASTBOOT USB anymore!!
so the pc doesnt recognise the device and i cannot use the all-in-one toolkit!
HOPELESS
c2nitz said:
when i plug the usb into my Windows 8 PC, it DOESN'T say FASTBOOT USB anymore!!
so the pc doesnt recognise the device and i cannot use the all-in-one toolkit!
Click to expand...
Click to collapse
I HAVE NO IDEA WHAT TO DO NOW...
USB CANNOT DETECT HOX+ NOW..
COMMAND PROMPT CANNOT FIND DEVICE..
TOOLKIT CANNOT FIND..
I have a new custom ROM downloaded finally (viper), but unable to sideload now..
The custom RUU failed to download halfway Twice, even if it succeeded, it won't detect device.
been doing more research... PdaNetA4013 downloaded but not able to install on this Windows 8..
i'm trying to re-download the AndroidSDK, just in case..
some kind expert pls help!
to me, this is all hell breaking loose.. its been almost 3 days now... big REGRET!
c2nitz said:
I HAVE NO IDEA WHAT TO DO NOW...
USB CANNOT DETECT HOX+ NOW..
COMMAND PROMPT CANNOT FIND DEVICE..
TOOLKIT CANNOT FIND..
I have a new custom ROM downloaded finally (viper), but unable to sideload now..
The custom RUU failed to download halfway Twice, even if it succeeded, it won't detect device.
been doing more research... PdaNetA4013 downloaded but not able to install on this Windows 8..
i'm trying to re-download the AndroidSDK, just in case..
some kind expert pls help!
to me, this is all hell breaking loose.. its been almost 3 days now... big REGRET!
Click to expand...
Click to collapse
well maybe go back try the basic things maybe ur pc isnt up to it recheck drivers mine was wiped all out and got it back

Samsung Galaxy Note II stuck at bootscreen [OS flashing?]

Well. It's my worst fear. Launched the DPI changer app, attempted to change my DPI (to a valid amount) and nothing happened, no big deal. My wireless connections stopped working and my shop stopped working. I downloaded a different DPI changer, everything was working except Google Play. I attempted everything then decided to tell it to "change" my DPI to default. Went to reboot then bam.
I get the following:
The standard splash with the Verizon 4GLite then it goes on to loop at the Samsung splash for a bit then loops from the beginning (4GLite).
I've tried getting into "recovery" mode but it won't go, I do not know why. (Vol up + home + power). Need help please, thanks.
(Noob alert, if you mention anything that I might need, if you could please supply a DL link to minimize any more mess ups I might make)
EDIT: I got into recovery mode I forgot you were able to remove the battery (I was panicking, I apologize) I am also rooted with 4.2
EDIT2: I've attempted a factory reset, nothing new happened.
EDIT3: I need to reflash an OS. I'm really freaking out. It says I don't have a bootloader (OS).
Bottom line: This problem kinda... multiplied itself most likely based on my own stupidity. I'm keeping it at the "Team Win Recovery Project v2.5.0.0" recovery menu because I don't even want to boot into anything. Awaiting instructions.
Solkrieg said:
Well. It's my worst fear. Launched the DPI changer app, attempted to change my DPI (to a valid amount) and nothing happened, no big deal. My wireless connections stopped working and my shop stopped working. I downloaded a different DPI changer, everything was working except Google Play. I attempted everything then decided to tell it to "change" my DPI to default. Went to reboot then bam.
I get the following:
The standard splash with the Verizon 4GLite then it goes on to loop at the Samsung splash for a bit then loops from the beginning (4GLite).
I've tried getting into "recovery" mode but it won't go, I do not know why. (Vol up + home + power). Need help please, thanks.
(Noob alert, if you mention anything that I might need, if you could please supply a DL link to minimize any more mess ups I might make)
EDIT: I got into recovery mode I forgot you were able to remove the battery (I was panicking, I apologize) I am also rooted with 4.2
EDIT2: I've attempted a factory reset, nothing new happened.
EDIT3: I need to reflash an OS. I'm really freaking out. It says I don't have a bootloader (OS).
Bottom line: This problem kinda... multiplied itself most likely based on my own stupidity. I'm keeping it at the "Team Win Recovery Project v2.5.0.0" recovery menu because I don't even want to boot into anything. Awaiting instructions.
Click to expand...
Click to collapse
I saw you posted this in the att forums but I think I can help. Just download any ROM and flash it. Twrp has a failsafe now that will basically prevent you from bricking your phone if no os is detected. Do you have an external memory card? If you do transfer a ROM to your card, put it in your device, and flash it. Your not bricked.....your just soft bricked. Or you can always go back to stock. I'm sure your device thread has instructions on how to Odin back to stock. Hope this helps
Sent from my SGH-I317 using xda premium
roughneckboren said:
I saw you posted this in the att forums but I think I can help. Just download any ROM and flash it. Twrp has a failsafe now that will basically prevent you from bricking your phone if no os is detected. Do you have an external memory card? If you do transfer a ROM to your card, put it in your device, and flash it. Your not bricked.....your just soft bricked. Or you can always go back to stock. I'm sure your device thread has instructions on how to Odin back to stock. Hope this helps
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So if I wanted to flash stock, I just need to put the stock rom on my ESD put it into my phone and flash it from the recovery menu? Is there more to it than that? Or do I need to do that all externally with "Odin"? Where would I obtain the stock rom? And thank you for your response.
Solkrieg said:
So if I wanted to flash stock, I just need to put the stock rom on my ESD put it into my phone and flash it from the recovery menu? Is there more to it than that? Or do I need to do that all externally with "Odin"? Where would I obtain the stock rom? And thank you for your response.
Click to expand...
Click to collapse
I'm talking a touchwiz ROM one of your developers has made. You can find it in your forums. It sounds like you don't have much experience with this stuff. Did you make a nandroid backup at all?
Sent from my SGH-I317 using xda premium
roughneckboren said:
I'm talking a touchwiz ROM one of your developers has made. You can find it in your forums. It sounds like you don't have much experience with this stuff. Did you make a nandroid backup at all?
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Sadly, no. I didn't. You are correct, I am very new to this sort of thing, I've rooted other devices before (simple one click only, I'm good with computers, but not smart phones) but nothing has blown up this bad before. I've placed this rom (http://forum.xda-developers.com/showthread.php?t=2261478) on my ESD however, when I put my ESD back in, it reads it as blank. I'm assuming I need to relaunch recover mode to refresh its directories. However I'm very scared to do that because I have no OS anymore.
Solkrieg said:
Sadly, no. I didn't. You are correct, I am very new to this sort of thing, I've rooted other devices before (simple one click only, I'm good with computers, but not smart phones) but nothing has blown up this bad before. I've placed this rom (http://forum.xda-developers.com/showthread.php?t=2261478) on my ESD however, when I put my ESD back in, it reads it as blank. I'm assuming I need to relaunch recover mode to refresh its directories. However I'm very scared to do that because I have no OS anymore.
Click to expand...
Click to collapse
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
---------- Post added at 03:43 AM ---------- Previous post was at 03:40 AM ----------
roughneckboren said:
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
Click to expand...
Click to collapse
Edit- If none of this works then you'll probably have to adb sideload your phone to transfer the rom to your internal SD card. Otherwise you can ODIN back to 100% stock which involves a huge download and you'll have to reroot your phone. If you don't know how to ODIN to stock then get on youtube and there are plenty of videos to help you along. The basis for the note 2 (att, verizon, sprint,....) should all be the same just a different file to download.
roughneckboren said:
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
---------- Post added at 03:43 AM ---------- Previous post was at 03:40 AM ----------
Edit- If none of this works then you'll probably have to adb sideload your phone to transfer the rom to your internal SD card. Otherwise you can ODIN back to 100% stock which involves a huge download and you'll have to reroot your phone. If you don't know how to ODIN to stock then get on youtube and there are plenty of videos to help you along. The basis for the note 2 (att, verizon, sprint,....) should all be the same just a different file to download.
Click to expand...
Click to collapse
I rebooted into recovery. I only hesitated because it warned me I didn't have an OS. That worked, I saw the ROM and am now flashing it. I will edit and let you know if all works.
EDIT: It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Solkrieg said:
I rebooted into recovery. I only hesitated because it warned me I didn't have an OS. That worked, I saw the ROM and am now flashing it. I will edit and let you know if all works.
Click to expand...
Click to collapse
Please do.
ROOTBOXED!
roughneckboren said:
Please do.
ROOTBOXED!
Click to expand...
Click to collapse
It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Solkrieg said:
It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Click to expand...
Click to collapse
No problem man. Not everyone here is a butthole. Its not a pain because I was there once too. Just make sure you run a backup in twrp. You can name it too! Just practice and read around. Watch YouTube videos (I learn by visual)
And I keep my backups on PC in case a memory card goes bad. If you wipe system in recovery make sure you flash a ROM because system is obviously your OS and twrp prevents it from booting and bricking your device. Good choice on the recovery. :thumbup:
If it will at least boot to something there's always hope. be sure to hit the thanks button. It always helps. Glad to have gotten you up and running. If you need more help just pm me.
ROOTBOXED!

[Q] Need help installing clockwork recover on my Atrix HD MB886

Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.

Samsung S3 memory full

My work colleague is an idiot - Despite warnings from his S3 that phone memory was low he continued taking videos and pictures and he has no sd card in the phone. Now the phone boots up but the pattern unlock screen is unresponsive. I offered to try to help him as he said "The last 2 years photos of my life are on there" so clearly a factory reset will lose them all so that's not an option.
So I installed Kies, thinking I'll just grab them to my PC for him - but alas no. MTP USB driver installation fails every time and yes I've googled my socks off, tried all the regedit fixes, even tried installing Win 7 32 bit on a spare hard drive.
I've checked that the ribbon connector for the screen is attached, tried linux boot disks that don't see the phone and now I'm all out of ideas. Any help would be vastly appreciated :fingers-crossed:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
You may can flash a custom recovery or a temporary recovery(not sure because I don't know what is available for the model you're working with and what isn't), if you can get one of those recoveries then you may can use the factory reset in recovery(it wont wipe his photos) or adb to get the phone working.
Remember to create an XDA account so you can post and reply in the forums.
Droidriven said:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
Click to expand...
Click to collapse
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Azarameus said:
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Click to expand...
Click to collapse
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Droidriven said:
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Click to expand...
Click to collapse
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Azarameus said:
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Click to expand...
Click to collapse
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Azarameus said:
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Click to expand...
Click to collapse
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Azarameus said:
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Click to expand...
Click to collapse
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I showed him this thread at work earlier and although he growled somewhat at being called an idiot in my OP, he had to agree he was lol. It turns out he bought his partner the same phone around the same time so I checked and it has Automatic upgrades ticked and is on build 4.3 so we can hopefully assume the problematic one is on the same version. When I mentioned the possibility of bricking to him he became unsure as to whether I should proceed with flashing. If he was to send the phone to Samsung themselves would they be able to retrieve his data safely, albeit with some cost and waiting?
Thanks again for your input
Hawaiihemd said:
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Click to expand...
Click to collapse
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Azarameus said:
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Click to expand...
Click to collapse
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Hawaiihemd said:
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Click to expand...
Click to collapse
Ok thanks again. I am going to attempt this tonight, will update on any progress
Azarameus said:
Ok thanks again. I am going to attempt this tonight, will update on any progress
Click to expand...
Click to collapse
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Azarameus said:
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Click to expand...
Click to collapse
Nice! And were you able to get the lockscreen working again?
Hawaiihemd said:
Nice! And were you able to get the lockscreen working again?
Click to expand...
Click to collapse
Yes indeed, all is working now as it should. The village idiot actually danced off to his car when I returned his phone - he has strict orders from me to move all his stuff to the SD card and make regular backups to his PC!
Thanks again - would never have done it without you guys

Categories

Resources