Hi, got a problem, long story short, cant acces internal storage in any way, tried to flash gapps for cmx by lloir but cwm and twrp dont allow me to do it in any way (fastboot flash, adb sideload zip), does anyone had similar problem or even better, found a solution?
myusernamewastoken said:
Hi, got a problem, long story short, cant acces internal storage in any way, tried to flash gapps for cmx by lloir but cwm and twrp dont allow me to do it in any way (fastboot flash, adb sideload zip), does anyone had similar problem or even better, found a solution?
Click to expand...
Click to collapse
Make sure your adb is up to date and supports sideload and make sure you have the proper drivers on your pc to recognize the hox+
Once those terms are met, flash TWRP and do the sideload process again and ditch CWM
Sent from my HTC One X+ using xda premium
yes, adb is up to date, it supports sideload, there was no other way to flash rom (which is quite logical), i am using linux, screw windows-style "proper drivers" (and yes, I have proper drivers), adb/fastboot devices returns me serial code for plugged phone and yes, tried to sideload that zip in twrp (sending ok, writing failed) and in cwm (dunno, adb sideload gapps.zip didnt work anyway). I acctualy tried to figure out whats going on before posting, but nothing helped :/
P.S. I woke up sick today, which is bad for my stretched program, so I may be a bit rude...
i assume you have "enabled" sideload in TWRP
advanced > sideload
or you can just adb push filename.zip data/media/0/whatever.zip (if you use 4.2.1 just remove the 0) within the recovery without needing to hit sideload
yes, i have enabled sideload, in cwm, device was not found, in twrp terminal quoted sending ok, writing failed
adb push was I think endless waiting for device, or error (cant try it again right away, dont have hox+ here), but i am not sure i tried right path when i am looking at data/media/... :/ will try in few hours
You can also just push the file to your sdcard and then flash by putting in adb push then the file /sdcard
Sent from my HTC EVARE_UL using xda app-developers app
Dunno if you cant read or what, but I cant just adb push or fastboot flash it, I cant put in internal storage by any mean I can think of thats whole point of this thread...
Yes I did understand bit mounting sd storage is not possible at the time , and if sideload does not work which I have experienced myself , adb push does work in recovery.
Sent from my HTC EVARE_UL using xda app-developers app
Finaly did it (several days ago, too busy to post)thx for help, but I have come to interesting problems... when I run camera, it just pops error saying that i dont have any storage to store photos and FC...
same problem - HELP!
myusernamewastoken said:
Finaly did it (several days ago, too busy to post)thx for help, but I have come to interesting problems... when I run camera, it just pops error saying that i dont have any storage to store photos and FC...
Click to expand...
Click to collapse
Hey, I have ran into the same issue with not being able to sideload any ROMs or zip files to my sdcard after flashing. How did you correct this issue so that the sd card is available and camer/etc work?
thanks for the help
mmgill said:
Hey, I have ran into the same issue with not being able to sideload any ROMs or zip files to my sdcard after flashing. How did you correct this issue so that the sd card is available and camer/etc work?
thanks for the help
Click to expand...
Click to collapse
I didnt solve it sofar, still trying...
P.S. somebody on national android forum told me to flash different rom, it should fix according to him, didnt seems to work... help anyone?
Can you tell why you say it is not working? Because you didn't find the ROM_NAME_FILE_YOU_SIDELOADED.zip?
Is this the situation?
Lucky Thirteen said:
Can you tell why you say it is not working? Because you didn't find the ROM_NAME_FILE_YOU_SIDELOADED.zip?
Is this the situation?
Click to expand...
Click to collapse
Hmm... topic name was solved out, now I have different problem described later, dont really get your post, its too late for combination of me and sarcasm and honestly i dont care about someone beiing sarcastic in forum, I was in plenty of flamewars and I grew up. If you wanted to say something meaningful, sry, didnt get it, eventhough my english is fine and I am smart guy.
@mmgill I solved it in a weird way for me (maybe someone can explain), I tried to flash paranoid android, flashing OK, but it didnt boot after really long time, so I decided to put there CMX by llior again (found out its sofar only rom working for me). And like a miracle, external storage was avaliable for camera, file managers, windows and ubuntu (after making whole MTP concept work in ubuntu). Will try to flash some other roms my friend wanted to use (I dont own HOX+, it resembles dining plate for me, its my friends phone and it was his first root ).
myusernamewastoken said:
Hmm... topic name was solved out, now I have different problem described later, dont really get your post, its too late for combination of me and sarcasm and honestly i dont care about someone beiing sarcastic in forum, I was in plenty of flamewars and I grew up. If you wanted to say something meaningful, sry, didnt get it, eventhough my english is fine and I am smart guy.
Click to expand...
Click to collapse
Well if you take some time to read all my posts you will understand that I wasn't making fun of you and never flame people. I do realize now that I forgot to quote mmgill when I responded (he PM'd me about this issue), this is where you got lost.
Greetings.
Ok, then I am sorry... anyway, problem solved by flashing another rom, its not really my phone, its my friends, we were unable to do this earlier, cos hes not as much educated in all this and he downloaded several roms, which were all for AT&T HOX+ (he has international version), I did believe him that he choosed roms compatible with his phone, but hes dumbass and I feel terrible to loose many hours of my time when I could write my thesis and even worse to not check it earlier after him (its honestly very stupid rookie mistake), it just occured to me out of blue while chewing tobbaco... Thanks for help anyway, some things said helped to resolve this issue much faster...
.
.
.
so dumb... and now I am typing fastboot flash boot XYZ.img in my dreams...
using the right version of TWRP
Just a thought, if this is still an issue for anyone. But if you aren't able to mount your internal storage make sure you have installed the correct recovery installed. You can check at the end of the .img, Sprint ends with M7wls, international ends with M7, and there are others.
If you don't have the correct recovery installed it may not load your storage.
Hope this helps,
Cheers.
Related
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app
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
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
vectorer said:
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
Click to expand...
Click to collapse
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
superbay said:
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
Click to expand...
Click to collapse
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
vectorer said:
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
Click to expand...
Click to collapse
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
superbay said:
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
Click to expand...
Click to collapse
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
vectorer said:
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
Click to expand...
Click to collapse
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
superbay said:
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
Thanks. It's HTC One X+, I got there from a Google search for sideload as I know zero about it. As it turns out it didn't work, got to 22% then failed every time. I'll check out that link now.
Thanks again.
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
vectorer said:
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
Click to expand...
Click to collapse
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
Click to expand...
Click to collapse
how would i do this operation??
now no matter what i try i get
error: closed
vectorer said:
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
Click to expand...
Click to collapse
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
vectorer said:
how would i do this operation??
Click to expand...
Click to collapse
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
vectorer said:
now no matter what i try i get
error: closed
Click to expand...
Click to collapse
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
superbay said:
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
Click to expand...
Click to collapse
thanks I'll keep trying this weekend
vectorer said:
thanks I'll keep trying this weekend
Click to expand...
Click to collapse
Just keep posting here to see how far your effort is with it. Good luck
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
vectorer said:
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
Click to expand...
Click to collapse
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
superbay said:
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
Click to expand...
Click to collapse
Well nothing is working.
I guess my device is a paperweight even if I can get into recovery.
Can't flash anything, not even the RUU, can't sideload........nothing.
Tried Hassoon's instructions for the RUU but it won't reconise that a device is attached to go into Bootlaoder, sideloading ALWAYS fails at 22%. Others seem to overcome this but I cannot. It's frustrating reading how many problems are solved when nothing works for me.
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.