Database Develop

[Q] Nexus One not start after root...

Hi all,
I have a big problem. I have my old Nexus One that never I root or modify. Today, after more than 1 year of use and reading various root guides I decide root my phone. My phone are updated from Google to 2.3.3 and say that is version GRI40. After finish all process of root the phone boot perfect and run perfect. Later I install also the Recovery-RA to can make backups, etc.
After this the phone not boot any more... Keep frozen at main screen with the big "X" and the padlock at bottom.
I can´t use any more my phone... any ideas or help? I forget one step?
I can boot perfect and run the Recovery(*) mode with Recovery-RA and all these options of this application.
All help are welcome!
THANKS!
(*) Recovery version is: RA-Passion-v2.2.1

Try flashing a new ROM, it sounds like it got corrupted when you installed RA. If you made a backup try restoring it, if not just do a factory reset and flash whatever ROM you pick.
Edit: You might also get more help if you ask in the Nexus forum.

OK, thanks!. I make a nandroid backup, that is the first that I try restore, but this not work. Now I try download any other. You know if exist exactly the same 2.3.3 that I have unmodified on my phone before I install RA? Thanks again!

There might be, just search for "stock ROM" in the nexus forum.

Thanks dbz!, I already use the GRI40_rooted_deodexed_busybox_apps2sd.zip that I found here and run again!!!
One more question: if I like on next update receive the update from Google that automatically update my phone like in the past before root, I can?

If you want to get an update from google you'll have to unroot. Usually when an update is released it isn't too long before a rooted version is released so just be patient.

You don't have to unroot the phone to get and install the OTA's in the future.
But when you apply a stock update you will loose root.
Sent from my Nexus One using XDA App

4.0.4

i have searched for 2 hours before asking
is there any difference between 4.0.4 official roms and if there is what is the best one i tried LRG open germany but my note freeze a lot on it

your note freeze cause of installation route you followed.
they are different cause of regionalization stuff. Knoone knows exactly what it means, cause Samsung has no external changelog
sent from my GT-N7000 using Tapatalk 2

yes, you have not followed correct method of installation. Flash a GB rom via pc odin, root it, do 3 wipes in recovery and then go ahead with new plans. Its a full proof method.
Each new release of Samsung rom is first covered here in this section...just search . Readers are eager to flash and announce the changes they see...like new keyboard look ( LR6), sim lock ( LRk), signature unlock, video popup ( LRG ), new root method etc etc, just read those threads.

thx for your help i have installed gb and flashed through mobile odin i now have cm9 on my note which is fine no freezes but everything that makes the note special is gone before that i had LRG but too many freezes i think the reason is too much apps i have about 500 because this is my first android device and i like to know everything about it
i use go backup for restoring the apps each time i dont know if this is the problem

michoayash said:
thx for your help i have installed gb and flashed through mobile odin i now have cm9 on my note which is fine no freezes but everything that makes the note special is gone before that i had LRG but too many freezes i think the reason is too much apps i have about 500 because this is my first android device and i like to know everything about it
i use go backup for restoring the apps each time i dont know if this is the problem
Click to expand...
Click to collapse
500 ??? :angel: Feeling like I will have the whole world in my note if I would follow you. I have only 210 applications including system lol

Do not restore backups unless you know what your doing.. The best software for restoring apps its titanium backup and you gotta activate the unknown sources option.. Also you gotta create a filter in order to only Backup your apps and data not system apps or data..
Enviado desde mi GT-P6200 usando Tapatalk 2

Dr Ketan has written a very guide on how to back up and restore. OP, plz check his signature.

you are talking about this
http://forum.xda-developers.com/showthread.php?t=1837984
i actually don't use nandroid backup so i don't trigger the brick bug
and i dont like titanium backup because as i said i have about 500 app and using titanium i have to press install and done for each one
gobackup is much easier to use and more simple and i can save everything including sms, wireless passes, call log
and i use nova launcher so all my homescreens and ui is backup
if you would like to use gobackup do not install the latest version it keeps giving force close

michoayash said:
thx for your help i have installed gb and flashed through mobile odin i now have cm9 on my note which is fine no freezes but everything that makes the note special is gone before that i had LRG but too many freezes i think the reason is too much apps i have about 500 because this is my first android device and i like to know everything about it
i use go backup for restoring the apps each time i dont know if this is the problem
Click to expand...
Click to collapse
well cm9 says in first post dont restore...
Go to recovery, clean with format system, data and sdcard on safe kernel recovery, better take out external so you dont wipe that.
wipe cache and dalvik
then instal cm9.
dont use backup for recovering apps cause: first post says so
and because different version roms use different data structures, you are bound to run into errors
because just because.
Sent from my GT-N7000 using Tapatalk 2

Issues With Touchpad

Hello, I have had a touchpad for some time and but CM9 and CWM on it some time ago, but it started having some issues recently. So I figured I should try and reinstall a newer version of CM and start from scratch.
I went to this post http://forum.xda-developers.com/showthread.php?t=2026692 and downloaded both the skz+tenderloin-1.10.zip and the gapps zip.
I then placed those into the Download folder on the touchpad.
This is where things took a turn. I rebooted to get into CWM, upon selecting it from the boot menu it kept restarting back to the boot menu. After a few tries it got into CWM. I then wiped the data and did a factory reset, wiped the cache, and then wiped the dalvik like the post said to do. I then went to install zip from sdcard. Found the skz+tenderloin zip and chose to install that. CWM says it starts to install but then before the progress bar fills up at all...it resets back to the bootloader.
At this point I am at a loss with what to do and I would really appreciate any help I can get with this.
UPDATE: I figured starting from scratch would be the best bet, so I have uninstalled CM9 and CWM using ACMEUninstall. Now I am wondering if it is worth using CM10 as my default Android or should I stick with the best CM9.
Either way, if I should use CM9 or 10 can someone either help me or point me in the right direction for the best tutorial on doing this properly?

Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .

sstar said:
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
Click to expand...
Click to collapse
The issue I am encountering is there is a ton of info out there, some outdated some not. I restored back to stock webOS with nothing else. I have ACMEInstaller 3 in the Palm directory, so I am ready to install the most stable/best CM9 currently out there, I just don't know which tutorial is the best one to follow. Could you perhaps just link me to one you recommend?

http://rootzwiki.com/topic/31548-ho...-with-sound-camera-microphone-updated-232013/

Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.

Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I installed CM9 based on the link above with the AIO package. It worked flawlessly, hopefully my freezing/restarting issues happen less often now. Thanks to all who offered help.

Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I can tell you that I use my Schizoid as my daily driver, and it's not a preview.

[Q] Can we verify whether or not our backups have been corrupted?

Hey guys, I just have a general question that (seemingly) applies to all Android phones. I'm posting this question in the GS3 mini section because I have a MetroPCS Galaxy Exhibit [SGH-T599N] and I guess that's where we're we've been relegated to, but this question, as I said, could really apply to any phone. My question is this: how can I verify that my NAND backups are not corrupted?
Here's some context: I recently flashed to CM 11. Everything's running great, it's my daily driver, and I love it. It's easily the best, most smooth ROM I've ever used but I recently discovered a need to flash back to the stock ROM backup I was running pre-CM 11. Before I flashed to CM 11 I was running the standard JB stock and incidentally I was also using a different Kik username. After flashing to CM 11 and installing Kik, I decided to make a new username. Now, given that I never logged out of that old username (the one I was using on JB stock), I know that if I were to flash back to that old ROM, I'd boot into a ROM that's logged into that old account. I need to be able to do this because I need to access that old Kik account's chat logs for personal reasons. My problem now is due to two issues: my amazing stupidity and...well, no that's really it.
At the time I was running stock I was running CWM recovery. I made a backup using Rom Manager but like an idiot I backed up to my internal SD card. In order to flash to CM 11 I had to wipe my internal memory, which eventually lead to me losing that backup. My only silver lining is this: I made one backup to external sd about a week before I flashed to CM 11.
Here's where it gets messy: Not knowing that the backup on the external sd was for my stock pre-CM 11 ROM, I stupidly deleted it to free up space and began saving files onto the external sd card. After I had flashed to CM 11 I made about three CM 11 backups. I deleted my pre-CM 11 backup because I mistook it for one of these three CM 11 backups. Upon realizing the height of my stupidity, I just finished recovering these lost folders and files using a data recovery program, but I have no idea whether or not the files have been irreparably corrupted. Is there any way I can verify that this backup is still good to use? I don't want to risk attempting to flash back to my old ROM only to have it wind up bricking my phone. Does anyone know of a good way I can figure this out? Any help is appreciated.
Thanks,
an idiot

adamryanx said:
Hey guys, I just have a general question that (seemingly) applies to all Android phones. I'm posting this question in the GS3 mini section because I have a MetroPCS Galaxy Exhibit [SGH-T599N] and I guess that's where we're we've been relegated to, but this question, as I said, could really apply to any phone. My question is this: how can I verify that my NAND backups are not corrupted?
Here's some context: I recently flashed to CM 11. Everything's running great, it's my daily driver, and I love it. It's easily the best, most smooth ROM I've ever used but I recently discovered a need to flash back to the stock ROM backup I was running pre-CM 11. Before I flashed to CM 11 I was running the standard JB stock and incidentally I was also using a different Kik username. After flashing to CM 11 and installing Kik, I decided to make a new username. Now, given that I never logged out of that old username (the one I was using on JB stock), I know that if I were to flash back to that old ROM, I'd boot into a ROM that's logged into that old account. I need to be able to do this because I need to access that old Kik account's chat logs for personal reasons. My problem now is due to two issues: my amazing stupidity and...well, no that's really it.
At the time I was running stock I was running CWM recovery. I made a backup using Rom Manager but like an idiot I backed up to my internal SD card. In order to flash to CM 11 I had to wipe my internal memory, which eventually lead to me losing that backup. My only silver lining is this: I made one backup to external sd about a week before I flashed to CM 11.
Here's where it gets messy: Not knowing that the backup on the external sd was for my stock pre-CM 11 ROM, I stupidly deleted it to free up space and began saving files onto the external sd card. After I had flashed to CM 11 I made about three CM 11 backups. I deleted my pre-CM 11 backup because I mistook it for one of these three CM 11 backups. Upon realizing the height of my stupidity, I just finished recovering these lost folders and files using a data recovery program, but I have no idea whether or not the files have been irreparably corrupted. Is there any way I can verify that this backup is still good to use? I don't want to risk attempting to flash back to my old ROM only to have it wind up bricking my phone. Does anyone know of a good way I can figure this out? Any help is appreciated.
Thanks,
an idiot
Click to expand...
Click to collapse
if you recovered it immediately after deletion - then it's most likely still good. I don't think there's any way to fully verify backups; but I will say this if you do chose to use that backup and it fails, you should easily be able to flash any rom over again to correct it, or even use odin to go back to stock rom and try again. The only way you truly hard-brick phones is flashing something over usb and it gets disconnected haflway through, or you accidently flash somethign to the wrong partition (if you were using hiemdall), generally speaking for nearly 80% of bricks are sem-bricks and should easily be able to recover from.

Exothermic said:
if you recovered it immediately after deletion - then it's most likely still good. I don't think there's any way to fully verify backups; but I will say this if you do chose to use that backup and it fails, you should easily be able to flash any rom over again to correct it, or even use odin to go back to stock rom and try again. The only way you truly hard-brick phones is flashing something over usb and it gets disconnected haflway through, or you accidently flash somethign to the wrong partition (if you were using hiemdall), generally speaking for nearly 80% of bricks are sem-bricks and should easily be able to recover from.
Click to expand...
Click to collapse
Thanks for your quick reply, Exo. I'm curious, do you think inspecting the .log file would be able to give me an indication about the integrity of the backup? In going through old backups I was able to open the .log file in Notepad and read in plaintext what was written there. If this could be used as an marker of the backup's health, then it seems I may be out of luck as the .log file for this backup seems like nothing but jibberish. I've opened it with Notepad, Notepad++, and I even installed a different third party program that's reads .log files exclusively (called Baretail), all to no avail. I'll try flashing to this backup in the meantime but I'm curious: do you think attempting to read the .log file could be a good way to verify the backup's integrity, or is there something I'm missing here? Thanks for your time.
Adam

First you should make a nandroid of your current ROM (CM I presume) so that if you brick your phone while trying to restore the stock backup, you'll still have the CM backup to restore if something goes wrong and the phone can't boot or says that there's no os installed.

Help a newbie; LG Optimus L90; learning to flash

Current situation: pretty much complete newbie. I broke my factory OS after rooting it, I think I deleted something Settings needs, so anytime it needs to access settings I get "Unfortunately, Settings has stopped." I factory reset it hoping that would help, but now after loading it gets stuck on a cycling white screen reporting that error (I think it's trying to set up the phone.) The error message prevents me from doing the touch-four-screen-corners trick I've read about and bypass set up. So, stuck on phone setup errors as near as I can tell.
I do have my user apps backed up with TiBu, but couldn't get the recovery zip from TiBu to work. I downloaded CWM but didn't figure it out yet. Also unfortunately I can't get the USB drivers to work (the LGE Android MTP Device won't install), so I think my only way of getting files to my phone now is using the microSD cards.
I'd love some help! I think my factory OS is FUBAR, so I'm not trying to fix that, instead I'd rather just get a cool ROM loaded so I can continue learning with a working device with said cool ROM. I don't fully understand terms that I know I need to like "bootloader" or what CWM / TWRP actually does or how to use them (I need to make a custom recovery ROM?). Or where to get a cool ROM or which to pick, some step by step basics on from some experienced users would be fantastic! Thank you so much!

So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...

lfom said:
So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...
Click to expand...
Click to collapse
Thank you, this put me in the right direction. I ended up discovering that even though the " LGE Android MTP Device won't install," the flashing process worked with this program via USB anyway. I'm going to lick my wounds a bit before trying to flash a custom ROM. Thank you!

For the rom installation, after unlocking your bootloader and rooting, download the app Flashify from Google Play, then install TWRP or CWM zip file as recovery image. Then, from there, you can install custom ROMs or make backups of your phone, etc. A cool custom ROM I recommend is CyanogenMod, it ports newer versions for older devices. So, you can have Android 6.0.1 in your phone