Related
Hi,
I've had a HTC Hero since they came out, and for most of the time I've had it, it has been rooted and running various roms (Cyanogen, lately).
A few weeks ago I somehow got dust under the screen, sent it to HTC who repaired it and sent it back, with their own 'install' which has:
Firmware: 2.1-update1
Software Number: 3.32.405.2
Now, I'm not really a fan of sense and would like to go back to using Cyanogen mod, however, I can't work out how to root it (well, to get it to a stage where I can flash it with custom roms).
All of the tutorials and step-by-step guides on here and ones I've found on Google don't seem to work any more (I believe they do on earlier versions of HTC's build), I appear to have got as far as 'rooting' it but when turning on with power and home held down I get the red triangle/exclamation mark displayed. I'm clearly not doing something right.
I don't want all the answers spelled out for me, but if someone could give me a hint as to where to look or a clue as to what I could be doing wrong I'd be grateful.
Any help will be appreciated
have you tried the androot method
http://theunlockr.com/down/UniversalAndroot-1.6.2-beta5.apk
http://www.megaupload.com/?d=FJA3L8YZ
make sure that unknown sources is checked
after you have download it and put it onto your phone download astro file manager and then find the androot apk and install then open it then press root
after doing that download to the android market and search rom manager and flash the recovery image that way
I had, yes - actually it was the first method I tried.
The first time I ran it, it said 'woot you're root' (or something similar) but on rebooting and holding home and power, I got the red triangle/exclamation mark symbol.
I have since reset my phone to factory settings so I reinstalled it now, again it appeared to root successfully, but on rebooting and holding home/power it just says on the white HTC logo screen and doesn't appear to progress.
Would the easiest solution to be to attempt to revert to a previous 'official' HTC build and then try Androot again? One of these maybe?
hmmm did you try the goldcard method? was the only method to gain root access on my Google G2 Touch (german HTC Hero by t-mobile)
due to most providers lock the possibility of rooting, this maybe could help you...
look for "Goldcard tool" @ google... sry don't know where i got my tutorial from the days i rooted but i remember it wasn't hard to find(although i was a complete rooting noob these days), so should be no problem to you
greets, Summoner
edit: was thinking... the exclamation mark looks like a missing custom recovery, maybe you need to flash one.. i'm using AmonRA 1.0.7.1 (build number correct? don't know) which can be found around here on the forum.
I was a Hero user some months before. I tried official 2.1 update just to root it again. I used this guide: http://www.villainrom.co.uk/forum/showthread.php?3941-Rooting-my-new-HTC-Hero&highlight=root+hero
I used amon ra recovery then. I also ended up getting red triangle. This was solved when i formatted my sdcard and only put the recovery image.
I had the same symptoms, could only get amon ra installed via rom manager alternative install, it would then allow me to reboot to recovery once, but every other time I would get the red triangle.
I believe the problem was I had two recovery.img files, stupidly I had copied a recovering flash image onto the sdcard, then renamed it recovery.img, not realising its name was then recovery.img.img.
(its been 20 years since I've administered unix systems..and it shows).
perhaps check the recovery img you have, and where it is, and re-try the command line flash, it might not be a rooting issue, hth.
LM<FAO
sorry for laughing but this is a thing that happened to me when i was a beginer
REMEMBER THIS rooting doesnt mean u have a rec image remember use androot to give u super user then use rom manager to flash clockworksmod recovery image then reboot in recovery
jave PHUN
wishes the best for all your heros
Thank you all kindly for your assistance; after hours of trying, tears, tantrums and almost throwing my phone out of the window I'm up and running on Cyanogen Mod again
Thanks!
no problem remember to press the thanks button to who ever helped you
hmm I've done fallowing:
1. androot
2. rom manager - flash clockworksmod recovery image
3. reboot in recovery
4. backup
5. wiped cache/dalvik
6. installed Elelinux-7.0.0-RC2-Hero-v1.6 (2011-03-23)
and now the android logo keeps looping (more then 5 min)
/cry
Hi,
I have an lg c800 -- mytouch q by lg
I rooted it yesterday and removed all the bloat. I also installed several root only apps to optimize the phone.
It ran smoother than even right out of the box.
So, I figured it be a good idea to backup the rom, and maybe later try cyanogenmod... So I installed Rom Manager by clockworkmod
It said i needed to install clockwork recovery rom. I went in there but it said my device was unsupported (only like 12 were) so I backed out,
and stupidly hit TWRP listed under "Recovery Already Installed". (thinking that meant what options I had to SETUP a recovery/backup)
I hit backup rom. almost instantly the phone restarted. After the bios, but before android it went to a screen with a box, and an arrow pointing from the inside of the box to the little android man. Then went to the regular android boot screen.
It does this every reboot now. The SuperSU is still there, whenever Rom Manager (which I have to reinstall each reboot) asks for root access I get that dialog box, so it hasn't actually hard reset the phone I don't think. But all the user data, contacts, apps, wifi passwords, google id "(to access Play) get wiped out.
I understand what I did wrong. I think I understand what its doing (booting to the factory rom as it was, and I can't set it to stop doing it each reboot)
What I need help with is getting back, if possible, to what I had previously, among other things, I had a bunch of tasker profiles and notes that will be time consuming to replace.
Thank you for your help.
EDIT: SuperSU is now listed among the factory installed apps. This is unchanged each reboot.
Question: If I unroot the phone what that invalidate Rom Managers ability to run before android boots?
where the people at?
dosmastr said:
where the people at?
Click to expand...
Click to collapse
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
dosmastr said:
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
Click to expand...
Click to collapse
OK so its not in the guide, but one is to exit the shell BEFORE keying adb devices. it does show.
but sadly I don't think this gets me closer to fixing what is broken.
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
dosmastr said:
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
Click to expand...
Click to collapse
more info: the bloat from the original rom is still gone, and SuperSU is intact and functional
Chui says its some flag in CWM that isn't getting cleared when the device boots.
I'm just trying to get the data my apps help at this point.
cmon phone nerds i still need some help!
no help.
The original ROM of your phone got modified after you rooted, hence no bloat and SuperSU intact even after many wipes.
I suggest re installing the factory ROM again, including the bootloader, radio and other stuff. That ought to fix the issue.
What phone do you have ?
So when it was modifying the rom that was running at the time, also the recovery rom was modified?
how do you reinstall factory rom if the phone never enters fastboot?
I'm all about wiping the bootloader (so it STOPS running recovery) but I have only made a little progress in finding how to do that without fastboot.
What I can do is run a root viewing file manager. I even found the log for the recovery it keeps running. But not what to kill so that it STOPS recovering.
Phone is LG C800DG
The LG rom update software has a recovery option but that didn't work.
One youtube video
http://www.youtube.com/watch?v=nDFO6H1XObI
Says I can get around this by using a flash utility the installs as an apk. I doubt I'll find one compatible with this phone though as support is very limited.
looks like everything out there says I need a 3rd party recovery already flashed...so that I can flash a stock rom.
sounds like the damn chicken and egg to me, to get stock fixed you need 3rd party but since you have stock you cant get 3rd party
It seems to be a general problem with your set as many others too have posted the same issue.
For stock ROM this should work.
http://forum.xda-developers.com/showthread.php?t=1825818
And a flashing guide
http://blog.androidia.net/8/how-to-flash-stock-lg-rom/
You can also see these for CM9
http://wiki.cyanogenmod.org/w/C800_Info
and
http://forum.xda-developers.com/showthread.php?t=1801622
Dumb e3 recovery. There been any updates on the cwm recovery? Thing takes forever to backup and restore rom
Hello community
sorry for bothering, but it's two days I'm stuckl with a problem and... zilch.
last day my phone, an O2 Galaxy Fame, ran out of battery (damn me) and decided finally to enter perpetual bootloop. Sometimes when rebooted took like 2, 3 hours to get out of the loop, today it's already 24 hours and more of bootloop. I can log into the recovery system (CWM, installed today in a desperate try to gain root access).
I would like to perform a reset, but doing so I would lose all the details of the Exchange mail and the wireless setting. that wouldn't normally be a problem, but tomorrow I'll be outside the country for a 3-day meeting and I'd need to read the mail. and configure the phone again, that is; is there a way I can force myself into the phone, gain superuser access and retrieve the files I need? I can read and understand adb shell commands, I'm not completely noob on linux and can follow guides.
There is so much mess in the android rooting - IMHO. at this moment I'm stuck with "adb cannot run as root in production builds" and can't sideload Superuser.apk from the recovery sideload screen.
If you could help me before tomorrow it would be great!
thanks!
Seems like a bit of a tough spot there. So it seems like you won't be able to access root that way due to the kernel blocking it. You'd essentially have to have to split the kernel, then decompile the ramdisk and edit default.prop and change ro.debuggable to 1, then recompile and flash the kernel.
So the phone goes into bootloops whenever it runs out of battery? Seems like kind of a big design flaw or a serious bug. Since you now have CWM, you can try and just see if clearing the cache and dalvik cache + fixing permissions might help. Won't make it any worse and won't wipe any important data. Other than that, maybe see if there is a stock rom that's exactly the same as the version you have and flash it over top of your current set up while wiping the caches. If that doesn't work, then you can try to wipe the caches and /system and reinstall Only do this if you know the rom works or you have a way to reload it completely via the PC - so this is a last resort because without /system, you have nothing to boot to!
I've no way to test this, but with most devices, if you have CWM installed, you can flash the SuperSU zip from Chainfire to root the device ( http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip ), but this will not necessarily allow you to do anything in recovery still if the kernel does not let you mount adb via root without making the other changes.
thanks, I've returned today from the business trip but since there is no IT today, this leaves me some more time to try with what you said - I'll let you know how goes.
Well, SuperSU loaded and for a brief second a "apps are starting" popup came out. Better than nothing!
but I'm stuck into bootloop as well.
My tought is: if I flash the same android version on the phone again, won't this delete the /data folder as well?
...I came up with one thought: there isn't any recovery distribution acting as a full android? can I trick android with Odin installing android on the recovery partition, so that it boots into that, and from that with su powers recover what's left in the "main" area?
I'm thinking it as a hard disk with two main partitions, one with android and one with a recovery system.... tell me if I'm wrong.
no one helping?
at least explining why?
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb