Develop Bugs

[Q] Relocking bootloader mac problem

Hello I am trying to relock the bootloader on my GN with a Mac. I am at the very last step where I have already unrooted and just need to reboot into the bootloader to relock it. Problem is, my volume down button is broken so I can't get into the bootloader that way and every time I put the command ./fastboot-mac reboot-bootloader, it keeps saying <waiting for device> Please help I need to return it because my volume down button is broken!

i dont know mac but.... you can do this several ways
1) adb reboot bootloader [ensure usb debugging is enabled]
2) download terminal emulator from market and open it and type in "su" (grant it access), then "reboot bootloader"
3) your ROM.. holding down power, may have "reboot" on it select bootloader.

You can't use fastboot commands unless the phone is in fastboot.. therefore, ADB reboot bootloader or the other two methods mentioned above.

Bricked, help needed.

Hello Forum!
Sorry for my English.
My Chinese Nokia N1 is bricked.
Why bricked:
After change file build.prop extracted from file uploaded by XDA user (I can't find a thread), my tablet only boot to screen "Powered by Android".
Nokia can't do power off. Allways reboot after many seconds hold power key.
Next what I do:
ADB working, but i dont have permission to change this file (i have backup build.prop).
I do all (IMO) to change permission to /system (read-only):
- mount -o rw,remount ...
- adb remount
etc.
Don't work power button and volume down.
And I have an idea ...
I run script to root Nokia from XDA.
Look great.
From recovery menu I mount /system to read-write.
After adb shell and mount command i see /system is read-write, but any changes/copy file = operation not permitted.
I try (of course after su).
- busybox mount -o rw,remount ...
- busybox chmod 777 /system
still "operation not permitted"
I'm disappointed.
And I run system/factory reset from recovery menu after run root script.
Now:
- still boot to screen "powered by android"
- adb not working, I don't have device ADB in Windows device manager
- power and volume up give me device: moorefield in windows device manager
- downloaded "Intel Phone Flash Tool Lite", and I see my Nokia after power & volume UP is connected in this software.
What next, what I need for unbrick? If they can...
Please help.

what's your current version?

Xkernels said:
what's your current version?
Click to expand...
Click to collapse
A5CN51C

you're better than me, my device can not even enter recovery mode, it keeps on turning and turning around after Powered by Android animation

Still needs help. I donate if my problem resolved.

Mine was stuck at "power by android" screen, it keeps looping to that screen.
Took me a few days of trying different things, I found the tablet was showing up on "adb devices" when it boots to "power by android" screen.
It shows up after maybe 30sec - 1min after you get to that screen.
When you run this command "adb devices"
If your device shows up.
You can run "adb reboot bootloader" or "adb reboot recovery"
If you device doesn't show up, you will have run "adb kill-server", otherwise it will never show up.
then run " adb devices" again.
Try a few time, if this works, you're in luck.
After you get into the bootloader, you can get into recovery mode, and use sideload to flash a full image.
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529
Pick a full size image newer or the same to your current version.
adb sideload image_filename

kourcomp said:
Mine was stuck at "power by android" screen, it keeps looping to that screen.
Took me a few days of trying different things, I found the tablet was showing up on "adb devices" when it boots to "power by android" screen.
It shows up after maybe 30sec - 1min after you get to that screen.
When you run this command "adb devices"
If your device shows up.
You can run "adb reboot bootloader" or "adb reboot recovery"
If you device doesn't show up, you will have run "adb kill-server", otherwise it will never show up.
then run " adb devices" again.
Try a few time, if this works, you're in luck.
After you get into the bootloader, you can get into recovery mode, and use sideload to flash a full image.
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529
Pick a full size image newer or the same to your current version.
adb sideload image_filename
Click to expand...
Click to collapse
Thanks You for answer.
I do a lot reboot after system/factory reset from recovery menu, and i never got adb device in windows device manager.
Without this device I do not have the ability to gain access to the adb device.

Teathring issues..:(

After successfully flashing roms like Cm, DU, and other based on MM os I enabled WiFi hotspot to share my internet but other device is unable to connect with my teathred network...What should I do...?

You have to unlock it because it's been locked in marshmallow for saving data.
Boot into fastboot mode by pressing Vol+ and Power button.
Open fastboot files and enter into adb and type the cmd as like below to enable tethering
adb shell
Then enter the command as like below
Settings put global tether_dun_required 0
That's it just reboot ur device ....
Now you have working tethering

coolraviskpec said:
You have to unlock it because it's been locked in marshmallow for saving data.
Boot into fastboot mode by pressing Vol+ and Power button.
Open fastboot files and enter into adb and type the cmd as like below to enable tethering
adb shell
Then enter the command as like below
Settings put global tether_dun_required 0
That's it just reboot ur device ....
Now you have working tethering
Click to expand...
Click to collapse
adb commands on fastboot? I dont think going to fastboot is required

What ever it may be ..u just run the command to unlock tethering

Changed ROMS then wanted to Downgrade Boot loop ISSUE

Can someone please help me?
Im currently using Jasminrom v7.0 with N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.md5
I came from v 4.4.4 but my recovery does not seem to work boot loops even with factory wipe. Unit shows download mode and recovery mode boots as well.
What would be the direct step to downgrade to a stock rom or any lower rom that you might suggest 5.0 and have root. MM seems to have bugs with Wifi and camera.
Thanks for any help if possible I would like to avoid the whole king root or kingoroot step if I can just keep the developer mode like it is currently
Cheers! :laugh:

hxxp://i66.tinypic.com/29nfiqc.png
hxxp://i64.tinypic.com/5aglu.png
(Doesnt let me post pics with http)
I do not know what I have done.
I know I had to root 2x and did the following:
On your device:
1. Make sure developer options and USB debugging is enabled on your device. Disable Reactivation lock. Also allow unknown sources.
2. Install Kingroot 4.8.5 (phone will reboot)
3. Verify root with root checker
4. Run the commands in the OP from the minimal ADB command prompt window
adb push unlock_n4 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 unlock_n4
chown root.root unlock_n4
./unlock_n4
5. Wait for phone to reboot. Shut down and battery pull.
6. Repeat steps 2 through 4. WAIT for phone to restart. Pull battery and SDCARD
7. Start phone in download mode (volume down, home and power) and check for Mode: Developer. If you have reached this point you are good.
8. Flash TWRP 2.8.5 via Odin 3.09 (put file in the AP slot)
9. Boot the device up, and copy SuperSU to internal storage.
10. Flash supersu from TWRP (reboot phone and enter recovery mode. hold power, vol up and home)
Then I installed partial firmware file on adp and ran the recovery of Jasmin Rom.
I NEED WIFI Working and Camera can someone point me to how to fix this

Please delete thread I fixed the issue by doing the following from marshmallow
http://forum.xda-developers.com/note-4-verizon/general/guide-how-to-install-kitkat-5-1-1-t3432452

[GUIDE] How to stop infinity bootloop to recovery

i found solution after several month, my device bricked to recovery with green blinking above the screen and it's infinity bootloop with no recovery and fastboot mode, so impossible to enter fastboot.
Q : what you should do?
A : you should prepare
1. driver and adb driver and fastboot driver,
2. you also need to open back cover and uninstall screen pin from it. and uninstall power pin and install it again.
Q: and?
1. install back cover with half installed, don't press backcover because we need install screen again.
2. plug the usb device to computer
3. in device manager you should see android bla bla this is possible to enter adb device.
4. check in adb with command :
adb devices
if device detected then go to fastboot
adb reboot bootloader
now our device is in fastboot mode, you should do this step:
fastboot -w
fastboot erase para
Q: and again?
1. uninstall power pin and install again
2. install screen pin
3. plug the back cover and press power button
4. your device now is unbricked!
bye bye infinity recovery bootloop!
i don't know this strange is happen to me when i uninstall pin it detected in adb. if you still not get in ,, try power + down button and adb device command.
i hope this tutorial work for you