Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again
If you can enter recovery do a factory reset
Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem
no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok
Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.
Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Related
Decided to help out and with the ok from ihtfp69 i wrote up a FAQ page
for everyone who uses Sky Raider Rom 3.3 Final
feel free to add.
zip is 180,304 kb
Sense 3.3 Requires a FULL WIPE
to avoid reboots make sure you have S-Off, Upgrade the radio to the OTA version
Wipe everything:
Factory Reset
Data Cache
Dalvik Cache
then apply SR 3.3
The initial boot animation is only there for the first boot and reverts to the original thereafter.
The fix for Rom Manager for fix permissions requires you to open Rom Manager once and then it will work after a reboot
Q: How to flash the ROM?
A:good info here... http://forum.xda-developers.com/showthread.php?t=709220
Q: Since 3.3 requires a full wipe, due to all the changes, I was wondering if the MM mappings for the rosie launcher are still compatible with this new release.
A: All of the mappings are new so make sure you clear out the old ones and download the new ones.
Q:how to Change your lock screens from adb or terminal shellLock
A: there are 13 different lock screens including the HTC one
You must be on SP1 or higher to use them
Change your lock screens from adb or terminal shell
Type 'tabunlock' or 'rotaryunlock' to get the menu seen below
Please choose from the menu - S-OFF REQUIRED
1) normal
2) normal+menu unlock
3) normal+trackball unlock
4) music buttons
5) music buttons+menu unlock
6) music buttons+trackball unlock
7) restore HTC lock screen
8) get me out of here!
reboot
Q: how do you get a logcat?
A: Run CMD prompt and in while in the root folder sdk/tools/ run the command "adb logcat" copy paste all you see onto pastebin.com and post the link. or download logcat from market
"HTC Mail Mod for EAS Admin Removal" You just go to settings -> security -> remove admin policy
Any chance someone wants to actually put this on the wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Droid_Incredible
There is a ROM section in there and would be a much better location than in a forum post.
What do you guys think?
supagene said:
Any chance someone wants to actually put this on the wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Droid_Incredible
There is a ROM section in there and would be a much better location than in a forum post.
What do you guys think?
Click to expand...
Click to collapse
up to our mod overground
Baseband version 1.00.03.03.06
hi
I am running SkyRaider 3.0 Sense RC3 but I have been unsuccessful in updating the radio. I've tried HBOOT but it doesn't like the image, tried renaming to update.zip, tried running the zip from Recovery.
Please advise.
thanks
Jack
Hello,
I would like to know what is "HTC Mail Mod for EAS Admin Removal". Is this some kind of feature?
I would like to disable the PIN Lock on my phone that is enforced by my companies security policy. I used to use LockPicker on Android 2.1 but that no longer works. Is there another solution for Android 2.2?
Thanks.
Nevermind I found it. You should add this to the FAQ. You just go to settings -> security -> remove admin policy (forgot the actual name since after I removed it, the option is no longer there)
Im having a couple of problems
1) I cant get my Yahoo mail account to set up, I have installed the Mail Mod from ROM manager.
2) I am trying to install an application from the market and i am getting the error saying I dont have enough space to install. I really dont have many apps so i dont think thats accurate. I have cleared the market's cache, data, and restarted the application, problem still persists.
Thanks for the help
surfboard3r said:
2) I am trying to install an application from the market and i am getting the error saying I dont have enough space to install. I really dont have many apps so i dont think thats accurate. I have cleared the market's cache, data, and restarted the application, problem still persists.
Click to expand...
Click to collapse
Check to see how many saved backups you have. Each backup can be upwards of 300mb's. If you have more than three that could be the problem. Happened to me once before. I got rid of a couple unnecessary backup files and freed up over half a gig of space. Apps from the market installed with no problems again afterward.
chrisloveskaos said:
Q: How to enable Tab Lock Screen with Sound Controls?
A: You need to remove the HTC lock screen to get to the underlying stock lock screen, get into Recovery, mount system, I go into adb shell to remove
cmd prompt
Code:
c:/sdk/tools>adb shell
~# (showsup) mkdir /system/app.disabled/
~# mv /system/app HtcLockScreen.apk /system/app.disabled/
~# exit
Click to expand...
Click to collapse
I keep getting stuck in a boot loop...
Stu_Gotti said:
I keep getting stuck in a boot loop...
Click to expand...
Click to collapse
There was a missing / between app and HtcLockScreen.apk
Can I just install SP2, or do I have to do SP1 first? ROM Manager is not pulling up SP1.....
gobluejd said:
Can I just install SP2, or do I have to do SP1 first? ROM Manager is not pulling up SP1.....
Click to expand...
Click to collapse
i thk just 2 is fine
Hi I just loaded skyraider 3.3 a couple days ago and tried out the lock screens, and up til now I've had no trouble loading the service packs or the lock screens thru ROM Manager but after activating a lock screen and rebooting thru terminal, I'm now stuck on the boot animation, batt pulls don't work, and I can get to recovery but I don't know what to do from there. Please HELP!!!!
m89maru said:
Hi I just loaded skyraider 3.3 a couple days ago and tried out the lock screens, and up til now I've had no trouble loading the service packs or the lock screens thru ROM Manager but after activating a lock screen and rebooting thru terminal, I'm now stuck on the boot animation, batt pulls don't work, and I can get to recovery but I don't know what to do from there. Please HELP!!!!
Click to expand...
Click to collapse
You have to let it sit for a good while... mine took like 5 minutes after changing the lock screen.
Is it normal for it to take up to 3 hours to complete? Cuz that's what keeps happening
Sent from my ADR6300 using XDA App
m89maru said:
Is it normal for it to take up to 3 hours to complete? Cuz that's what keeps happening
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no only 5 mins maybe
Can you update this ROM please? I dont have any bugs that need fixing, but i realllly love this ROM and my A.D.D kicks in if i dont make some sort of change
Already added circle battery and 6bar hehe
Update what exactly though? If you have no bugs then the Rom is fine.
Sent from my ADR6300 using XDA App
m89maru said:
Update what exactly though? If you have no bugs then the Rom is fine.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes i know
How about the lockscreen update? I think he asked if there was any interest, i would love it! Basically eliminate the lock screen altogether
rsarno said:
Yes i know
How about the lockscreen update? I think he asked if there was any interest, i would love it! Basically eliminate the lock screen altogether
Click to expand...
Click to collapse
There icons that can b changed through metamorph. I made mods to mine with colored icons like bluetooth, car mode, sms, gmail, email. Two kinds of email- basic email app icon r have one made for me for yahoo. So now when I get a email a yahoo icon pops up in my notification. Ask a themer to make you some. Themes and apps has some. I suggest using sysinterwolf cuz he is the man.
Found by laidaxin , from w.w.w.591fan.c.o.m
for us that are noobs, what exactly is this?
dingding2012 said:
Found by laidaxin , from w.w.w.591fan.c.o.m
Click to expand...
Click to collapse
Doesn't work for me.
Sent from my MB860 using XDA App
thebluetoothkid said:
for us that are noobs, what exactly is this?
Click to expand...
Click to collapse
Its supposed to be a working recovery for flipside. I can't get it to work however.
Sent from my MB860 using XDA App
I tried and it was a working recovery for my 508.
I installed it.
when reboot, I continued clicking the volumn down button, and the entered.
Sorry for my poor English.
dingding2012 said:
I tried and it was a working recovery for my 508.
I installed it.
when reboot, I continued clicking the volumn down button, and the entered.
Sorry for my poor English.
Click to expand...
Click to collapse
I am able to do all that also, but can't backup and can't install anything. I get error can't mount data/recovery and aborts.
ok... so i'm trying for the 100th time to install this silly thing... and for some reason... when i try to run it... it kicks me out...
i'm not sure what i'm doing wrong...
when i attempt to pause the install process... i get a screen full of if i type adb without an argument...
if someone could gimme a hand with this or tell me what the hell i am doing wrong... i'd appreciate it...
i wanna try to get laidaxin's cm7.2 working on my phone...
i dunno if it matters... but i am attempting to install from a windows xp machine...
Hello!
First, Thanks to all people around this work, specially Laidaxin for good work.
Well, sadly... I also still stuck on install the FlipSide recovery option of the first post... I did all te proccess by eleven times, testing different details that may be not clear for me (as run as administrator, with abd CMD screen closed and opened, if the version of adb never shows me the logs that appears in cmd screenshot... several times I got on the FlipSide the screens talking about su and later 2ndinit script got superuser permissions... but the screens of cmd generated by the script are so fast that was not able to read or check if the 2ndinit script was succesfull or if there something else that may be failing/missed... so by now still no luck)
as a resume, in hope that may help to test from new friends around here:
1) I reflashed my FlipSide to stock with sbf from the other thread tutorial (I use sbfflash in linux and everything works fine, using Power+UParrow in keyboard to enter in bootloader mode my Flipside)... and then I insert my SIM and SD card wiped with only the CM7-Laidaxin.zip file on it, ...complete setup as minimal possible in order to be able to set USB mode to memory access, and turn on usb development in applications menu.
2) Then I ROOT with SuperOneClick version 2.1.1!!! and connect my phone in normal use screen home (NOT bootloader mode!) with UBS debugging turn on and with USB mode set to memory card access (NOT Moto Portal No Media access...), the other methos with Z4root and newer versions of SuperOneClick FAILS for me...
3) I then try to install recovery with Laidaxin installer and procedure, but as I said after some attemps I still not success in get the recovery working, also try diferent ways... removing battery then reboot with VolumeDown pressed, Turn off normal and repeat, turning ON AND AFTER see the Red Moto press the VolDown key short time, later maintained it long, then pressing it several times, etc...
So, I made this resume in order to share info from my side and hope to save some time to other friends that may want to test the CM7 from Laidaxin, than in fact seems like a GREAT work for our Flips... so please if any help to get this fully working and tested will be very gratefull...
Best regards!
Ok... since I still can't get the automated installer working... I would really appreciate if someone could direct me to the forum/website that that installer came from... I would love to try to push it myself... but I'd have to do some reading...
Sent from my MB508 using Tapatalk
rignfool said:
Ok... since I still can't get the automated installer working... I would really appreciate if someone could direct me to the forum/website that that installer came from... I would love to try to push it myself... but I'd have to do some reading...
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
Hi!
Ok, I am not totally sure, but I suspect that this is the original link of this recovery, however, just now I need to go to my work, so, I do not have chance right now to check it, but hope may be usefull.
http://forum.xda-developers.com/showthread.php?t=944543
Best regards!
You should be able to install it like this:
- Extract everything in the "data" folder into a folder called "bootmenu" on your sdcard
- Then use either "adb shell" from a command prompt, or Terminal Emulator on the phone should work:
Code:
su
cp -R /sdcard/bootmenu /data/bootmenu
cd /data/bootmenu
chmod 0755 *
./install.sh
And it should say "Install complate...."
You can also remove the folder(s) if you want:
Code:
rm -R /data/bootmenu
rm -R /sdcard/bootmenu
Then to get into it, reboot the phone and once the notification light turns on, hit volume down
You my friend.... are the ****ing man...
FYI
Use the touchpad to select
Sent from my MB508 using Tapatalk
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
rignfool said:
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
I ran into the same problem but mine also stopped me from installing any other rom to test, run, or otherwise. I'm at a standstill in terms of helping test.
rignfool said:
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
laidaxin's rom replaces this recovery with one that doesn't quite work perfectly yet...
You should be able to boot back into CM7 and re-run the above commands and it'll work again
That doesn't change anything for me... it still won't unmount system...
I think if I read the output from the script install...
Our recovery installs to system... since Motorola doesn't love us
Sent from my MB508 using Tapatalk
Maybe try "rm -R /system/bootmenu" then install it...
rignfool said:
That doesn't change anything for me... it still won't unmount system...
I think if I read the output from the script install...
Our recovery installs to system... since Motorola doesn't love us
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
It does the same for me, which is what's keeping me from trying CM7, as I have no way to restore my current nandroid. The defy installs their recovery to /system as well and I gather that it works as intended, I wonder if it's that we need our own build of CWM. Do we know if whoever built CWM for the defy has their source tweaks available?
Unless you have something irreplacable in your /system or /data... I would just have RSD lite and an sbf ready... and take the plunge...
Because....
When you use CM7... apps2sd moves not only the apk... but also the lib files to the sd card...
As long as you switch the 'network operator' to GSM only (in wireless and networks)... laidaxin's kang runs beautifully... much much faster than stock
Sent from my Filpside using Tapatalk
Link2SD has no problem moving the lib files in our stock rom... I'm no stranger to reflashing with RSD Lite, it's just tedious to get everything set back up JUST right, and this is exactly the kind of thing nandroid is great for.
i am very sorry to ask this silly question
i found that i cannot use some apps on 4.2 , but the apps can be used on 4.1
thank you very much
Sent from my GT-I9300 using xda app-developers app
rooted or not?
not rooted
Sent from my GT-I9300 using xda app-developers app
then you're in a bit of a problem.....I was rooted and reverted back to 4.1 after I felt blowing my n7 with 4.2 up.
I don't know any other way apart from wiping it clean, which you could do by rooting it, which would save your apps + data
IF ANYBODY HAS BETTER KNOWLEDGE......PLEASE CHIME IN
This is what I did after I had the problem....root it, then backup all apps + data using titanium back up.....then copy the whole titanium backup folder to computer to save it all.....then reset back to 4.1.2, restore titanium backup, restore apps.....enjoy (and memo to self: if it ain't broken, don't fix it)
apart from rooting it I don't have any suggestions, sorry. wait for others if you want. Please note that this isn't a full proof method so I wouldn't like to be blamed for anything that goes wrong
ace9988 said:
then you're in a bit of a problem.....I was rooted and reverted back to 4.1 after I felt blowing my n7 with 4.2 up.
I don't know any other way apart from wiping it clean, which you could do by rooting it, which would save your apps + data
IF ANYBODY HAS BETTER KNOWLEDGE......PLEASE CHIME IN
This is what I did after I had the problem....root it, then backup all apps + data using titanium back up.....then copy the whole titanium backup folder to computer to save it all.....then reset back to 4.1.2, restore titanium backup, restore apps.....enjoy (and memo to self: if it ain't broken, don't fix it)
apart from rooting it I don't have any suggestions, sorry. wait for others if you want. Please note that this isn't a full proof method so I wouldn't like to be blamed for anything that goes wrong
Click to expand...
Click to collapse
thank you for answing
But the problem is that i do not know how to downgrade to 4.1.2
Sent from my GT-I9300 using xda app-developers app
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
phatmanxxl said:
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
Click to expand...
Click to collapse
Yea that tool kit really saved my butt a couple of times when I needed to back to stock android. I made sure to give a donation for the work he did.
phatmanxxl said:
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
Click to expand...
Click to collapse
Hi,
tell me if i understood correctly..... now that i have still 4.1.1 is better i do root, backup and nandbackup and after upgrade to 4.2, so in case of proobs i can come back.. is it right?
PS: actually my Nexus is completely empty
Which software u suggest, consider im no expert
Many thanks and sorry for my english
Ale
Take a look here
http://forum.xda-developers.com/showthread.php?p=34389960#post34389960
How to downgrade to 4.1.2 - very simple!
charlie135246 said:
i am very sorry to ask this silly question
i found that i cannot use some apps on 4.2 , but the apps can be used on 4.1
thank you very much
Sent from my Samsung GT-I9300 Galaxy SIIIusing xda app-developers app
Click to expand...
Click to collapse
I am a 11 Year old Girl and now i'll give you an instructions how to downgrade very easily.
I do already know the scams and battery problems with 4.2!
Question:Which OS do you have got on your Galaxy S3?
If you've got Android 4.0.4 IceCreamSandwich, then it sucks.
Ok, here is it=:
You need to have your device connected to the PC with a cable to follow this GUIDE.
For this you'll need a Cable which is still working without loose connection or so...
One end is a USB-Input like on USB-Stickers and the other end is MicroUSB and schould fit in your device.
Such a so-called „Micro-USB-Cable"
It is recommended to use an USB 2.0 input in order to avoid compatibility problems such as compatibillity problems with USB-3·0 or so. .... .
1.Download the best and most easy to use Nexus Toolkit (-- )made by a symphatic programmer- WugFresh.
WugFreshs Tooklit is even better than SkipSofts and has more features and even better!
Download it here [ „ http://www.WugFresh.Com/Nrt "], new version 1.8.7 released today. 9'o clock (09:22:51) in GMT+1
I had 1.8.4 and yesterday the 5th September, i did upgrade at 15:56:59 GMT+1 to 1.8.6..
Click to expand...
Click to collapse
2. Install this Program.
3.Download the Factory-Image of the Nexus 7 2012.
You cannot actually have the 2013-Version because the 2013-Version came out with 4.3 [Only-WiFi] and 4.3.1 on the Mobile 4G LTE-Version
IF you have got the only-WiFi-Version then take this link:https://developers.google.com/android/nexus/images?hl=de#nakasijzo54k (Choose JZO54K 4.1.2, too bad, Google did exclude 4.1.0;4.1.1;4.20;4.2.1;4.4.1Kot49e E)
IF you've got the Cellular Nexus 7, then it is not possible because unfortionally the cellular version was launched with 4.2.0!
Information:
FileName=nakasi-jzo54k-factory-973f190e.tgz"
Version: 4.1.2
Build:„JZO54K"
MD5·Checksum:„d906b505ccae0d439839d3c5fafb137a"
SHA·1-Chécksum:973F190e25cbafc29d9739fbe0ffb64ed8946946
[.]9b.Chéérs! Cheers?
http://forum.xda-developers.com/showthread.php?t=176647
http://forum.xda-developers.com/showthread.php?t=1766475
See my posts and WugFresh's answers on the last few pages by pressing the [>>] button on the page selection for more information.
4. You need to launch this program and press Auto·Detect Device+Build OS or so...
If this does not detect your device, then try choosing Device (Nexus 7 2012 WLAN or WiFi so-called...) and your Android-Version Manually.
5.[Backup]
To do a Backup with a device with not unlocked bootloader, then choose „Android Backup"
Do not select the both tickable options (Shared data and SysApps+Data backup) or it won't work.
Choose a location to save the ADB-File and wait until the device is unlocked, then unlock the screen and optionally you can type a password to crypt your backup.
Then start and wait.
Here it's recommended to use newer versions of this program. 1.8.4 was stuck at 92.495 MB or so. 1.8.6 worked fine for me so 1.8.7 will work fine too!
If the progress has finished, then the program will show you a Window with detailled Information. I did even upload a screenshot of this and it is on the official Wug thread on Page 440. Link is ^^^^ûp!^^^^^wards.
If your device has got an Unlocked Bootloader then just choose „[Full NºAndroid°Backup /W/]" and done. Just root in the main menu and... done!
Click to expand...
Click to collapse
6.Go to the devices settings menu and tap on „Storage", then tap on ⁞ and choose the USB-Option. Enable MTP and go to the Devices storage with your Computer on Windows Explorer.
Choose all files and if it says that the time lenght is being „Calculated" then it'sa just counting files, stay patient and wait!
7.
When even this finished then... well, you're ready, now you can Unlock the Bootloader!
I and my heart hate the factory data reset!
The only things that you can't actually be able of backing up are the Systen Settings, the Home Screen LayOut and the internal data of the System Apps.
Example:
Chrome History
Download History
YouTube Search History (if you've got an account, then online on your YouTube Account NOTHING will be changd!)
G·PlayStor Search History
(Google Drive Files will not be deleted from online!)
GMail Offline Sync (don't worry, anything still available online!
and etc.
Except of this, you'll actually loose Nothing!
Click to expand...
Click to collapse
After unlocking the bootloader you can finally root your device but this is not required for downgrading.
Now go to the Programs Home Screen and Load your Costum-ROM.
Use your about 256 MB big downloaded file for this.
The Original Name:„nakasi-jzo54k-factory-973f190e.tgz"
Size:268.416.146 Bytes
Size on Disk Drive(r):268.419.072b.
Windows Explorer shows the file as 255MB; FireFox as 256 MB.
And now you're..... Done!!!!!!!! ( )C o n g r a t u l a t i o n s ! ! ! ! ! [/FONT]
If you want to Relock your bootloader:
A.OEM Stock
B.Follow stéps
C.Done.
If the Backup is smaller than the App Data would be, then i don't know if the file contents are compressed or not... WugFresh won't answer (anymore) because he's probably tired of my (loooooooooooooooooooooooooooooooooooooooooong ( )) questions. I asked too much, my mistake. I asked if compressed or not... but still no answer there!
In this case read the official Nexus WugThrèad for more Important information.
I am doing the same steps but i downgrade from 4.4.2! This Colour for the Status-Bar Icon loox better than this!!!!!
:=Helpabilitty
:=
I hope that my yesterday's Post actually could help.
If it was too hard to understand for you or anybody else,
you (or everyone else) can ask me whenever you want.
Then i'm going to help you agian.
If my Information could not help again, then ask me.
But i hope i could help you.
And i hope that even non-professionals are able to understand what i worte in the last post of yesterday.
I wrote a long text in the last post and it did take 20 Minutes but well... no problem, if WugFresh is tired of answering questions (from my own experience) then what you can do is:
Simply ask me as many questions you want and i'll try to answer them all.
If i don't know the answer, then i simply search on the Internet!
But thanks for Reading my posts on this site, Danke.
Hoffentlich konnte ich dir behilflich sein!
Hannah Stern said:
:=
I hope that my yesterday's Post actually could help.
If it was too hard to understand for you or anybody else,
you (or everyone else) can ask me whenever you want.
Then i'm going to help you agian.
If my Information could not help again, then ask me.
But i hope i could help you.
And i hope that even non-professionals are able to understand what i worte in the last post of yesterday.
I wrote a long text in the last post and it did take 20 Minutes but well... no problem, if WugFresh is tired of answering questions (from my own experience) then what you can do is:
Simply ask me as many questions you want and i'll try to answer them all.
If i don't know the answer, then i simply search on the Internet!
But thanks for Reading my posts on this site, Danke.
Hoffentlich konnte ich dir behilflich sein!
Click to expand...
Click to collapse
The method is clear but.. the post is from 2012.. i think the OP has solved the problem or maybe he don't even has the n7...
Hey guys,
I'm experiencing some serious case of bricking here. It is most probably caused of accidentally installing wrong .zip file that is actually not for u8800. When i try to go into recovery or regularly boot it up, i see the infamous green screen with blue and red blocks. My only possible interaction with phone could be done by pink screen cuz i think it's working.
Anyway, most of forums i've been on states getting the original image folder and putting the official Android 2.3.5 UPDATE.app to dload folder in my sd card, then booting up or going into download mode (which both do the same thing, starts the update process) without the battery attached and the phone connected to the pc via an USB cable. The only problem is whenever i try this, the update stucks on around 30% of the bar and when this happens, the red light switches on and off more frequently than before indicating there was something wrong with the process.
Am i doing something wrong here? What do you guys have else to offer? There is almost no forum left in xda, modaco and androidhelp that i didn't check out. I'm going to start throwing up threads here. Please help me!
If you can enter pink screen, you can try fullflash :http://forum.xda-developers.com/showthread.php?t=1971266
Ax1qwer said:
If you can enter pink screen, you can try fullflash :http://forum.xda-developers.com/showthread.php?t=1971266
Click to expand...
Click to collapse
I've already come across with these threads before, pointing out the only solution is via linux terminal but currently i have no access to any OS other than Windows. Is there any other way without installing Ubuntu?
dalpus said:
I've already come across with these threads before, pointing out the only solution is via linux terminal but currently i have no access to any OS other than Windows. Is there any other way without installing Ubuntu?
Click to expand...
Click to collapse
You can use linux live CD/DVD. No installation, only boot system from CD/DVD.
Ax1qwer said:
You can use linux live CD/DVD. No installation, only boot system from CD/DVD.
Click to expand...
Click to collapse
I decided to do it using Virtualbox but i had some problems specifying the directory of the .bin file (It's on desktop)
Here is the example command given:
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
My command:
[email protected] ~ $ sudo dd if=/home/myusername/Desktop/HUAWEI_U8800_FullFlash.bin
Am i coding wrong, incomplete or it cannot simply be done in Virtualbox?
dalpus said:
I decided to do it using Virtualbox but i had some problems specifying the directory of the .bin file (It's on desktop)
Here is the example command given:
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
My command:
[email protected] ~ $ sudo dd if=/home/myusername/Desktop/HUAWEI_U8800_FullFlash.bin
Am i coding wrong, incomplete or it cannot simply be done in Virtualbox?
Click to expand...
Click to collapse
Just follow the tutorial.
you must type "of=/dev/device_name" in command
with "device_name" is the device name alocated to the U8800. It can be "sdb", "sdc", "sdd", "sde", etc.
Ax1qwer said:
Just follow the tutorial.
you must type "of=/dev/device_name" in command
with "device_name" is the device name alocated to the U8800. It can be "sdb", "sdc", "sdd", "sde", etc.
Click to expand...
Click to collapse
Hey sorry for resurrecting this thread. It's just that i previously tried everything including linux terminal but it just didn't do it and i brought it to its maintenance service for repairs. You can close this thread now, nothing to discuss here. But before that, could you give me some ROM suggestions to install to my newly working phone. I'd appreciate if you specify the reasons to use them too. You can send it via personal message. Thank you in advance.
dalpus said:
Hey sorry for resurrecting this thread. It's just that i previously tried everything including linux terminal but it just didn't do it and i brought it to its maintenance service for repairs. You can close this thread now, nothing to discuss here. But before that, could you give me some ROM suggestions to install to my newly working phone. I'd appreciate if you specify the reasons to use them too. You can send it via personal message. Thank you in advance.
Click to expand...
Click to collapse
Hi, Now I am using AuroraSP + , very fast, stable and smooth, http://forum.xda-developers.com/showthread.php?t=2295318 very good for daily use.
MIUI V4 is good ROM too, I am going to test it this weekend and use it as my daily ROM http://forum.xda-developers.com/showthread.php?t=2029969
If you like JB, you can try coldblue_´s CM 10.1 http://forum.xda-developers.com/showthread.php?t=2337235 , but the ROM isn´t perfect.
Ax1qwer said:
Hi, Now I am using AuroraSP + , very fast, stable and smooth, http://forum.xda-developers.com/showthread.php?t=2295318 very good for daily use.
MIUI V4 is good ROM too, I am going to test it this weekend and use it as my daily ROM http://forum.xda-developers.com/showthread.php?t=2029969
If you like JB, you can try coldblue_´s CM 10.1 http://forum.xda-developers.com/showthread.php?t=2337235 , but the ROM isn´t perfect.
Click to expand...
Click to collapse
Hello again, did you have time to try out MIUI? What are your impressions?
I am finally in possession of my phone once again since the last time i received my phone back from its technical service, dumbass engineers nulled my IMEI after they fixed bricked ROM problem. After i got it back, i thought i could fix IMEI problem if i switch ROMs and installed AuroraSP+. It was decent but didn't really had time to fully explore it as i immidiately sent it back. And now they installed Android 2.3 firmware again, bah...
dalpus said:
Hello again, did you have time to try out MIUI? What are your impressions?
I am finally in possession of my phone once again since the last time i received my phone back from its technical service, dumbass engineers nulled my IMEI after they fixed bricked ROM problem. After i got it back, i thought i could fix IMEI problem if i switch ROMs and installed AuroraSP+. It was decent but didn't really had time to fully explore it as i immidiately sent it back. And now they installed Android 2.3 firmware again, bah...
Click to expand...
Click to collapse
Hi, my small review is on last page
http://forum.xda-developers.com/showthread.php?t=2029969&page=17
Managed to soft brick my Note 4. Set my dpi to 200, and my resolution to 720p. Apparently, it's just too low. Worked great when I set the values, but restarting the phone caused the brick. (It boots, but can't access anything. Unfortunately, I don't have my PC allowed as ADB, so I can't even connect from that state to ADB.)
So.
My idea to prevent full wipe, is to use ADB sideload OR ORS.
- Sideload. Make a "payload" that will replace the build.prop with the stock one.
- ORS. http://wiki.rootzwiki.com/OpenRecoveryScript
How do I actually do this?
Like the RecoveryScript seems to be a great idea, but from TWRP, I could not find a single build.prop file at all. There is a default prop, but it contains no resolution, dpi or whatever.
So I spent another few hours on this. I hate myself. And I hate the app's developer for being so careless.
- Flashed latest Samsung firmware hoping it will kill the software. Nope. It did not.
- Flashed the .zip for build.prop. NO effect.
The system has the correct DPI value so it must not be the issue.
- I think the app auto runs, and sets resolution. So I tried grep, but it cannot find the "1280" string anywher,e and I also removed the app from /data/app and /data/data.
- I cannot get MTP or ADB working in TWRP whatsoever. Huge letdown, but there is just no support. And without seeing what happens on the screen (it must be just my lockscreen there), I can't accept ADB connections either.
Well, so I went YOLO and cleared data. And... behold, NOTHING.
Did this retarded stupid program killed my phone? Holy hell.
Okay, so full entire wipe + reflash + full wipe, and now it works.
This app? Never again. The others are good on the market, so go for it.
App in question: https://play.google.com/store/apps/details?id=com.chornerman.easydpichanger
[ DO NOT USE !!! ]
Instead of wipes at Restore DPI: You can remove only of "com.android.providers.settings" at "/data".
Sorry but I have to resurrect this. I've played with dpi settings and now after reboot I cannot press enter when I type in my password as keyboard is partly off screen. TWRP is not working as it does not support Android 12. Any chance to resolve this beside flash?
Update: Connected keyboard via OTG cable and managed to unlock
Resurrecting this to offer another solution that doesn't involve any wiping/flashing/restoring-to-stock or messing with build.props
I used the same app as OP and feared the worst when I got stuck on recovery after changing DPI
This method allowed me to restore my xiaomi Redmi 9 with android 10
-You need to have a custom recovery installed
-"shell wm" commands don't work in recovery
You need to edit settings_global.xml & settings_secure.xml found in /data/system/users/0
You can do this by pulling&pushing the files to a PC using adb or editing in recovery using nano editor or something similiar.
Search for:
"display_size_forced" in settings_global.xml
"display_density_forced" in settings_secure.xml
Edit those with something close to your default values, then reboot and that's it!
Now that you're no longer stuck in boot you can reset resolution and density with the usual methods like adb or a better app
I hope this helps anyone else stuck in the same problem I was
mrmrva said:
...TWRP is not working as it does not support Android 12. ......
Click to expand...
Click to collapse
Where did you get a A12 version for which Note4?
Owning a N910F=trlte I don't find any higher than A11.
Don't have Samsung but Poco f2 pro and was looking for solution everywhere so posted here.