need help no os in nexus one - Nexus One General

i accidentally deleted my stock os in my nexus one. i found some stock roms but i keep getting this error every time when i try to install them
E:signature verification failed

What recovery are you currently using?
If it is stock recovery you will need to use the official google file and rename it "update.zip" and place it on the root of your SD card. Make you sure you visit the development section and read up on the procedures, as your radio version and recovery are not listed, its hard to tell from your post. If you are indeed in stock recovery...
Here is the original, official ROM http://forum.xda-developers.com/showthread.php?t=614057, make you sure you load it correctly. And of course...I am not responsible for anything that may go wrong. You will soon get the OTA update to 2.2 Froyo.
If your on a custom recovery, you should download a custom ROM. Some are based on the stock AOSP so if that's what you want you can find one like that and flash it through custom recovery after the triple wipe (factory/cache/dalvik). If that doesn't work try switching to the other custom recovery image. Aman-Ra is one, ClockWork is the other.
cheers

Related

Can no longer flash ROMS/ROOT

Hey guys, I am having some issues flashing roms through CWM as well as rerooting.
A bit of backround info
Device: GT-P7510
Started with latest OTA stock rom. I was wanting to use titanium backup to uninstall some bloatware.
Rooted successfully following the wifi only version forum post on how to root.
Did what i wanted, but now i wanted more.
Decided to try to get Jellybean on my device. Loaded into CWM - flashed - successful.
Now i ran into the issue of no flash support - needed for school work i do on my tablet. Tried to follow guide on installing flash.. did not work, tried the titanium backup method as well with no prevail.
Decided to flash back to ICS. I chose the CM9 ROM.
Loaded into CWM - wiped data / cache/ dalvik / Installed rom from SD card - flashed successfully
I noticed that my home button was not working. so after another data wipe etc. and re flash of the rom it did.
I then could not get googleplay to function just kept getting server error no matter what i tried. I tried installing apk from the web. did not work. and tried loading gapps.zip through odin. Installed other google apps that did work, just not google play..
So i was like holy hell. what to do now. Tried installing another ICS ROM ( the one that mimics jellybean)... It fails instantly after unloading package or something of that nature. I tried about 3 different roms and get the same issue.
So i then followed the guide to unroot - it required flashing the stock ROM through CWM . I tried this but got a status 7 error. Not really sure what that was so i found another guide.
The alternative guide had me load the original ROM for the device via odin. Worked great!!! I thought i was in clear sailing. Updated to the OTA ICS ROM. And then went to follow the root guide again. It acted as if it was rooted, but upon reboot option in CWM it says root access might have been lost.. do you want to fix. I tried both no and yes. Reguardless i do not gain root.
I tried flashing other roms through CWM - they all fail instantly ( not with any specific error messages ) just says aborted.
Any idea on what i may be doing wrong?
What version of cwm u using ?
5.5.0.4 works best for our tabs coz he has not got some verification for unsigned zips something like that .
Hmm i think the problem is when u updated ota it took your root away so i would suggest flashing cf-root again via odin
Just guessing though really strange, perhaps back up data on sd card and format it too i know its a pain but could help aswell
;/
Sent from my GT-P7500 using xda app-developers app
I was on 6. something. So that may be my issue.
I did try an older version v4.0.0.4 which was included in the guide i used but that did not seem to work either. I will download that version and see what happens.
As far as flashing cf-root. I am going to do a forum search but the method i used used the file Samsung_galaxy_tab_10.1_root.zip through CWM.
it is always risk to Odin back to stock and update OTA I have bricked 2 android devices by doing this .......once you install custom roms it is always better not to install official update ..... ur device is not rooted properly just go to unrooted stock rom if possible and later get root.zip then try rooting ur tab using it .......and this might help ...... forum.xda-developers.com/showthread.php?t=1474971..........
CHEERS
HIT THANKS BUTTON IF I HAVE HELPED

Question About Software Error Message

Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.

OnePlus 2 Stock Recovery

Can someone please post here stock recovery.img for OPT im now on TWRP but i want to install H2OS OTA normally.
Thank you so much
You may have chosen to keep the twrp recovery on your device from beeing overwritten by the stock recovery. This is done in twrp by renameing the "/bin/recovery.sh" (afaik).
Before installation OTA update checks for all checksums of files it will patch. So you will not only need the stock recover but at least to replace the recovery.sh with the original one.
Much easier way is to flash 2.0.2 full (not the OTA!), flash 2.1 OTA, flash SU and reboot in one session from twrp . I have done this and it worked without a problem.
Just make sure your battery is fully charged before
I'm getting an updated binary error. Started getting it in TWRP after flashing a custom kernel. Could you post your stock recovery? Or the stock kernel? (preferably the latter I suppose)
I've tried digging into the full 2.0.1 and 2.1 ROMs to find them, but I can't track them down...
Yes,i need the stock recovery
Well I need stock recovery because of hydrogen OS hope someone have it..
All you need is recovery paparapapa ahahahah
I managed somehow to have back stock recovery
When i flashed TWRP and then Gapps for Hydrogen OS it asked me to stop stock recovery to flash or something so i press dont stop, and voila im back on stock recovery
OnePlus 2 stock recovery -> http://forum.xda-developers.com/oneplus-2/general/oneplus-2-stock-recovery-t3217848

Starting the root, recovery and custom ROM procedure from KitKat (D80220d-HKG-XX)

I've read pretty much every source I can find on getting a custom ROM up on my LG G2, which I haven't even rooted in the past 2 and a half years. My warranty ran out a while back and I'm getting a bit bored with stock now, and I want to start flashing, but the last time I did this was with my old HTC Desire HD.
As you can see I'm on 20d on my LG G2. It's a Hong Kong version for some reason, lol. What I considered doing was the following: update to the latest Lollipop official ROM using the LG Flash Tool (it gives me an available update to 30d); root using the rooting app, install a recovery with AutoRec Lollipop, flash a thermal recovery from the installed recovery (very scared of my phone overheating, I'm even considering putting it on a large, fast-running fan while doing anything, read too much about the phone overheating and making the screen yellow); back up my phone's IMEI data; use the recovery to install a brand new (I'm hoping a Marshmallow) ROM. I also understood that I need to flash a bootstack to change my bootloader to a KitKat, because it can be "fooled" using the BUMP thing. Is that correct? Do I even have to update my phone to Lollipop in this case? Also, how likely is it to overheat while doing all of these procedures?
Thanks in advance!
Sorry for the necroing my old thread, but I have yet to do anything with my phone. I am also still on KK. I saw that I can start rooting and install TWRP from it straight away. After that I need to flash a bootstack, right? How likely is it that I can brick myself? By that I mean what could get mixed up to get a brick while flashing. Also, has anyone had overheating issues while doing root, recovery installation and flashing things (newer TWRP, bootstacks, new ROM)?
Hi, i can understand your situation as i was in same till today, g2 with stock kitkat.
i finally installed cm13 after rooting it and the phone feels fresh.
you have understood most things right and ready now.
you dont need to upgrade to lollipop if youdont want to, you can start from kitkat itself.
few things i can tell you to begin here,
Root your G2,
for kitkat i found few good methods. Either do it via ioRoot using pc. or you can use towelroot or kingoroot apps to do it from phone itself. I used kingoroot since i didnt have a system with me. You can find these apps by searching at google, jst tyoe kingoroot. At first i was skeptical but it worked nice.
after root, you download autorec app, this is to install a custom recovery(twrp) for kitkat. you just have to install the app and run it and press install recovery/twrp and it'll do the rest.
after you have twrp installed, you need to upgrade it to latest version. For that download blastgator's twrp for your model and flash it through your recovery.
oh and dont forget to learn, how to enter into recovery yourself, since each G2 model has different method.
once you have these things you can start flahing roms. Most of the instructions on how to flash certain rom with what bootloader and bootstack etc. is written in its own thread, so you can learn that from that rom's thread that you will flash.
but basically, you need kk bootloader and lp bootstack for cm13 and above. usually both these things come in one zip. (if not you check for hybrid bootstacks)
Just make sure you are downloading things For your Model, if you try to flash different models stuff into yours, itll brick.
The autorec app, blastgator's twrp and ioroot can be found in a sticky thread in G2 general section, along with many other files and guides in that thread, theres complete index in that thread of all thing for all g2 models .
here : http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
also usually the phone doesnt heat up while flashing, just make sure your battery is more than 80% before you start and itll be ok. Even if it does a little, after a custom rom itll be fixed. I suggest you try cm13 for starters as your first custom rom.
hope this helps you :good:
Good Luck ::highfive:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
hitmancho said:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
Click to expand...
Click to collapse
to upgrade from kitkat you need lp or hybrid bootstacks. they have images (. img files) that are needed for your phone to function properly., like aboot, modem, radios etc. Hybrid bootstack contains aboot from kk and everyhing else from Lp. So when youll flash a bootstack, youll need to wipe everything, except internal storage(or external if you have one) , before you can flash it. that wipe will include, cache, dalvik cache, system, data. so basically all the old system stuff will be gone before you can flash this bootstack. i hope after reading that youll know that you cant access your old kk installation since itll be wiped, therell be nothing to boot to. if youll try, it will give you errors on lg logo.
understand it like this, to install new 21 inches tyres to your car, you need to upgrade the rims to hold a 21 inch tyre right? what will happen if you just put the 21' tyres on old 15' rim or old 15' tyres on new 21' rims?
the cm 13 devs dont recommend you to flash bootstacks because most of the models took the official lollipop update, which put everything in their phone to lolipop level. since there is no official marshmallow(MM) bootstack for our phone (because no official update), everyone developed ways to utilize lollipop bootstack to function on a custom MM Rom. Since most models are already on lollipop, theres no need to flash lollipop bootstack while flashing custom rom. That step is mostly for those who are still on stock or custom kitkat based rom. So they say to get official lollipop through kdz method, instead of flashing Lp bootstack before gettig their rom. But remember if a rom developer asks to install a bootstack for their rom, you should consider it if you dont have much knowledge about it, cause if you dont follow instructions, you can soft brick, in that case youll need hybrid bootstack.
see if you are using everyhing proper for your phone then your phone wont brick. only thing that can go wrong with that condition is your execution, your steps. As long as you dont make a mistake in these steps everything will go fine.
ill explain it what you should do.
1. first root your phone.
2. when done rooting, install "root checker" from google play. itll confirm if you have root or not.
3.Then you come back here and find autorec app from the link i gave you in my previous reply. download that, install the autorec app. and follow on screen instructions and itll install twrp recovery for you.
4. then come back here again, and find blastgator's twrp, from the same link in previous post. itll be the one whih says "twrp with f2fs". download it and remember where you put it.
5. turn off phone, boot into recovery (i hope you've learned by now how to get into recovery of your g2 model). Now youll be in recovery, hit install button there and find where you put that file, flash it, then reboot recovery, youll have new recovery after that. then you reboot into system.
now upto this point, you can play along in your kk, have fun with features, say last goodbyes and all lol. Because everything stock kk related will be gone, past this point, including all the apps you have installed.
[IMPORTANT] : after rooting and installing recovery, get bootstack zip, rom zip and gapps zip files downloaded and placed together in a folder on your phone, before you start with flashing bootstack. Because you wont be able to boot back into system after flashing just bootstack.
now you prepare for MM, boot into recovery, now since you are in kk, you need to install LP bootstack, and for that you need to wipe everything using your recovery's wipe feature.
6. in recovery, hit wipe, hit advanced, select cache, dalvik cache, system, data. [ Dont select internal storage otherwise all flashing files will be gone and youll be left with a brick.] and wipe.
7. Now hit the back button to go back to main recovery screen once wiping is finished. hit install, flash the bootstack zip.
8. now your phone has new bootloader but its still empty, like you got a body but no soul . so hit back button, hit install and flash the rom zip you downloaded.
9. now flash gApps same way.
10. once its done, just hit reboot system. no other steps needed.
11. be patient, first boot takes longer than normal boot.
12.enjoy MM :highfive:
you probably know these steps from all the reading but its for your reference, so you dont screw up at all and be safe from bricking.
you can get google apps from opengapps website. you need to get ARM-> 6.0 -> (your prefered ones) pico/nano/micro/etc.. pico has the least amount of gapps, all important ones are there in pico, then extra will increase as you go up from pico to stock. stock has all the gapps. size will also increase as you go up. so choose as you prefer.
now once you have a cm13 /MM based rom, you wont need to flash bootstacks for other roms from next time unless the developer instructs to do so.
good luck
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
andrew2432 said:
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
Click to expand...
Click to collapse
cwm is clockworkmod, its a custom recovery. i think you meant CM 13, mm rom.
yes, the Cyanogenmod team have placed root access into the rom, so once youll be finished wih installing cm 13 rom, you can just go to settings, Tap build number repeatedly until a message will show "congrats you are a developer now". that'll open developer options in main setting screen Go into that and youll see root access. turn it on. youll have root.
you can check in root checker app to confirm root access for confirmation. you wont need super su app in any of these roms anymore.
your steps :
stock
1. root
2.autorec (for installing twrp on your phone) for kitkat its on forums, for lollipop its in google play. just get the one for your model, search for autorec in google play.
- blastgator's twrp requires you to have any version of twrp beforehand in order to install his version.
3. download and save blastgator's latest twrp, when youll go to download his twrp, itll be written there which one's is the latest version, just download that one and flash it through recovery.
4. Yes place all files in your phone, you can get gapps from opengapps.org/
select arm- 6.0- whatever size you like(, pico is lightest contains all essential gapps, stock contains every gapps)
5. wipe yes.
6. flash bootstack
7. flash rom
8. flash gapps
9. once gapps done, just hit reboot system.
10. enjoy
yes go for it when you have more than 80% battery, this is to ensure that all flashing steps go through without any issue, you dont want your phone to run out of juice while flashing rom do you that could cause soft bricks. so always keep battery more before flashing.
[IMPORTANT] : remember to read instructions of the rom you're installing and adjust the steps as instructed in there.
Goodluck :highfive:
Awesome, I forgot to.flash gapps prior to something I just did, not sure if it will cause increased global warming or thermonuclear war...update soon
@MarshisnotMellow
Gapps installed!! No Internet connection on the d800 and something sinister has happened to my unlocked WiFi Hotspot so I'll have to check for play store capabilities later!! Thanks for the help!!
I decided to go with the latest 29.10.2016 nightly of CM13 for my first run on this phone. Everything went through, no one died, lol. I'm going to start installing and restoring stuff now, get Xposed on, like I have on my TF701T tablet and trick out my phone's appearance. Just a note - after you install new bootstacks your phone's MAC address will change, so if you have a WiFi network with a MAC filter you might want to add your new address.

Help adding new rom to h910r full stock rooted room with twrp.

Please help I'm trying to add custom rom I am rooted with twrp running H910r. It seems none of the roms run on 910r and when I flash it goes to the flash screen forever and doesn't come out. However it will let me flash back to h910r.
FreeYourPhonesAmerika said:
Please help I'm trying to add custom rom I am rooted with twrp running H910r. It seems none of the roms run on 910r and when I flash it goes to the flash screen forever and doesn't come out. However it will let me flash back to h910r.
Click to expand...
Click to collapse
Try flashing the superv20 rom by going here https://hassaanmirza123.wixsite.com/superv20/downloads and look for the H910 varient of your phone, this should give you a custom rom.
Things to note:
1. Use this custom recovery for it to work and don't worry it's for your version of the LG V20 (H910)
https://androidfilehost.com/?fid=674106145207485129
Flash the recovery you just download via flashfire from the Play Store or within the custom recovery.
2. Flash the prerequisites if you have them from the v20 rom, if not just flash the rom. (I believe the prerequisites only apply to the V20 H918 but I may be wrong.)
3. Next, you need to select the rom you downloaded and choose the stock rom version in the aroma installer then select your options.
4. Make sure you use Magisk and also choose the Custom Kernel option VERY IMPORTANT.
5. Then reboot back to the recovery and flash the same zip again and choose the modded system UI selection, if you want or you could skip this and enjoy the custom rom without any modded system UI
That should do it. If something like failed to mount system or set permission failed. Just wipe everything but the microsd card if you have one and then repeat the steps above.

Categories

Resources