Hallo,
I've been trying to install the updated to update-cm-4.2.7.1-signed.zip.
I've been able to install first the signed-dream_devphone_userdebug-ota-14721.zip and imediatly after that, without reboot, the update-cm-4.2.7.1-signed.zip. Only I was unable to sign in to google right after that so I rebooted and then I was unable to boot it any longer...
Ok so then I retried the whole process but now after flashing the first signed-dream_devphone_userdebug-ota-14721.zip, wich goes ok, the second update-cm-4.2.7.1-signed.zip aborts the installation...
Next to it the installation of signed-dream_devphone_userdebug-ota-14721.zip isn't stable at all... after max one minute the phone crashes, so I'm unable to do anything....
I'm feeling extremely NOOOOOOBY!!!...
Which is probably how I'm supposed to feel...
Uuuugh....
Anyways is there anyone with hints about what I'm doing wrong here?
Thanks!
Greetings,
Geert
did u do a full wipe from CM recovery before putting on the google updates then cyanogen??? i had this issue and it fixes it?
Sorry for the late reply...
I tried to flash the recovery image of cyanogen but itÅ› not possible anymore....
There is no flash_image tool on signed-dream_devphone_userdebug-ota-14721.zip...
Also using fastboot, it says < waiting for device > till eternity...
my advice would be to start from scratch, get dreaming.nbh on ur sdcard. follow the instructions @ cyanogens wiki
i was having a world of **** on my G1 and just went back to RC29/RC7 and started again. if you have the files already on the SD card (CM recovery, official google, latest cyanogen mod) its simply a case of a few key presses.
dont forget to do the telnetd stage. i did and then wondered why i didnt have root access lol
ive never bothered with fastboot, usually just use ADB!
r|ktk|ng
Related
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
do a search for adb for dummies on this site. it should help
Buck Shot said:
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
Click to expand...
Click to collapse
did you try to load rom in the recovery img? This also happened to me (triangle with the android guy) and I thought I couldnt flash custom roms. For some reason the regular reboot to recovery mode gives me the triangle of death as you call it.
I got around this by loading in into bootloader mode then going to my command console, getting to my skd tools folder, and then typing
fastboot boot (whatever recovery img you used)
Then everything worked perfectly.
They are going to move this to General....
You did not follow the steps correctly it sounds.
Did you Load Amon Ras Recovery?
IF YES,
GO into Recovery
WIPE data
Flash Cyanogen's Latest ROM
Flash Google Apps available on Cyanogen's front page Post
In future ALWAYS nandroid Backup...
If you did not load Amon Ra's Recovery, you should go do this from fastboot.
I'll try to explain it to you:
1. The Bootloader is unlocked (you see the open lock at the first screen)? If you don't see the lock this is the first you should do or send it directly in for repair!
2. Then you have to flash the Recovery ROM (http://forum.xda-developers.com/showthread.php?t=611829) This you need to flash an update.zip Exact instalation guide is in the Link.
3. The ROM. If you want Stock then here you'll find it as an update.zip: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Choose one without includet Radio ROM!!! (See below why!)
4. Copy the ROM to your SD Card Root
5. Go into Recovery ROM (Vol Down with Power and then select recovery with the Volume button). There you select wipe and choose the first entry there (wipe data and cache)
6. Stay in Recovery ROM and selct Flash from update.zip and select the update.zip. Wait until everything is done and you are promted to reset your N1.
(DON'T MESS AROUND WITH THE RADIO ROM IF YOU DON'T KNOW EXACTLY WHAT YOU ARE DOING. DON'T UNDERSTAND ME WRONG, I THINK YOU HAVE NO GLIMPS WHAT YOU ARE DOING SO BETTER LEAVE THE RADIO ROM ALONE!!! YOU MAY BRICK (DESTROY) YOUR PHONE WITH IT!!! If you dont believe: http://android.modaco.com/content/g...odaco-com/303716/nexus-cannot-on-after-flash/)
7. There should be no 7. Everything should be fine by now.
Hope I could help.
** 100 Posts **
Stheoft u are my hero!!! Now hold do I get the multitouch update? lol sorry
DID YOU EVERY KNOW THAT UR MY HERRRRRRROOOOO
edit: i got it, im back to square one... thanks alot for all ur help
@ Buck Shot, this is a development forum... threads with question shud go in the general forum... these are making the development forum a mess....
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?
Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.
My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?
CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip
here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......
I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App
soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.
Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it
I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
wantpizza said:
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
Click to expand...
Click to collapse
I think you may need to root your phone again.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
wantpizza said:
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
Click to expand...
Click to collapse
No problem.
Another thing you could try and do is flash twrp via fastboot and see what happens.
Update twrp. twrp-3.6.2_9-0-h910.img
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset.
Thanks a ton @Darnrain1 !!
Yep - that was all I had to do to get TWRP back was fastboot flash it in and now I restored an old backup and have my phone back.
I appreciate it. Happy New Year and all the best.